[Info-vax] Volume Shadowing & Cluster Satellite

[Phillip Helbig---undress to reply]

In article <jn3dae$3rc$1 at news.belwue.de>,
gartmann at nonsense.immunbio.mpg.de (Christoph Gartmann) writes: 

> today I tried to fiddle around with volume shadowing on OpenVMS 7.3-2. 

You mean you haven't been using it up until now?!?!?!

> So
> far everything worked as expteced. The boot node's device changed from
> DKA0: to DSA0:. 

Right.  More precisely, it changed from NODENAME$DKA0: to DSA0:.  The 
allocation-class stuff has little to do with volume shadowing directly 
but is needed to make the disk name fit into the SCB.

> But the satellites were unable to boot from the "new"
> cluster system disk. I changed all references in SYSTARTUP_VMS.COM,
> SYLOGICALS.COM and in LANCP. Satellites did boot, entered the cluster but
> immediately afterwards before the beginning of STARTUP.COM they reported:
>     boot device is already mounted as a shadow set member

I'm not sure, but it's probably easy to create "new" satellites from 
scratch.

I have all physical disk names in exactly one place.  For a non-system
disk mounted early (from SYLOGICALS.COM) in SYLOGICALS.COM (OK, a copy
on each system disk) and for all other disks in a procedure in this
non-system disk.  That way, I can change it there and don't have to 
change it anywhere else.  (At the console, one still has the physical 
name(s) since the machine still boots from a single physical disk; early 
in the boot sequence the shadowset is rebuilt.)