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

[Len Whitwer]

On Apr 4, 2:41 pm, hel... at astro.multiCLOTHESvax.de (Phillip Helbig---
undress to reply) wrote:
> In article
> <6e2ac757-dacb-4e35-97eb-fea92c6d9... at pg6g2000pbb.googlegroups.com>, Len
>
> Whitwer <l... at psds.com> writes:
> > How do I avoid a full disk shadow copy when I shutdown/boot a node
> > back into the cluster?
>
> (DIS)MOUNT/POLICY=MINICOPY.
>
> > 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!!!!!
>
> That is what MINICOPY is for.  (It is groups of 127 blocks, not files,
> which have changed which is the basis.)  I went from 9 hours to a few
> seconds in such cases (slower hardware and smaller disks than you have,
> though, but the improvement should be about the same).
>
> Also consider MINIMERGE for unexpected problems.

Thanks for this info. Will continue and get back to you if more
questions.

Len