[Info-vax] Shadowing & Reboot

[Phillip Helbig---undress to reply]

In article <jp3feo$gt3$1 at online.de>, helbig at astro.multiCLOTHESvax.de
(Phillip Helbig---undress to reply) writes: 

> In article <jp30ou$lfk$1 at news.belwue.de>,
> gartmann at nonsense.immunbio.mpg.de (Christoph Gartmann) writes: 
> 
> > yet some more questions concerning shadowing of a non-system disk:

Sorry, I was thinking SYSTEM disk.

> > I created a shadow set with two disks, each disk connected to a different node.
> > So far so good. Then I rebooted node 1. When node 1 was up again, I had to
> > manually add its disk back into the shadow set. So, should I put this mount
> > command into SYSTARTUP_VMS.COM? 

I usually mount disks in a procedure called from SYLOGICALS.COM.

There are system parameters which determine how long systems should wait 
before kicking a disk out of the shadow set.  It's a trade-off: if the 
time is long enough, you can reboot, but during that time I/O will hang.

> Next, the remounted disk went into a full
> > copy state, although there were no changes made to the surviving disk on
> > node 2. Is this normal?

Yes.  How should the other node know that nothing had changed.  The 
solution is MINICOPY.