[Info-vax] How do I avoid a full disk shadow copy when I shutdown/boot a node back into the cluster?

[VAXman- at SendSpamHere.ORG]

In article <6e2ac757-dacb-4e35-97eb-fea92c6d9e15 at pg6g2000pbb.googlegroups.com>, Len Whitwer <len at psds.com> writes:
>Hi All:
>
>How do I avoid a full disk shadow copy when I shutdown/boot a node
>back into the cluster?
>
>Have two rx3600's with a SAN on each running OVMS I64 ver 8.4 with
>clustering and Volume Shadowning.
>
>When one node (Clustered) goes down and then comes back into the
>cluster a
>COMPLETE shodow copy action is initiated on there-join. This takes
>about 9 hours
>which is unacceptable. There has to be a way around this where only
>the files
>that have CHANGED get updated!!!!!
>
>Anyone have any ideas???

Shadow device is?  DSAxxx?

What devices are part of that shadow set?


I crash one of my systems regularly (development) and the shadow sets
all come up with mini-merge.  Very quickly, all of my shadow sets are
available.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.