[Info-vax] ANOTHER minicopy question

[Keith Parris]

On Sat, 29 Dec 2012 10:19:21 -0700, Phillip Helbig---undress to reply  
<helbig at astro.multiclothesvax.de> wrote:
> I'm wondering how to set up MINICOPY on a system-disk shadow set,
> considering that it is not explicitly mounted during the startup
> sequence and is mounted by the booting node before any other node can
> mount it.  HELP says:

If you try to reboot a node from its local copy of the system disk  
shadowset, you're doomed, because when the node gets far enough along in  
boot to discover that it has booted from a now-out-of-date copy of the  
system disk shadowset, it will do a bugcheck of some sort regarding  
inconsistent shadowset state and leave the cluster.

You might consider a combination of two things:
1) Set up Automatic Mini-Copy on Volume Processing (AMCVP). This requires  
OpenVMS version >=8.3 (plus Shadowing patches to fix the initial bugs an  
AMCVP). With AMCVP, you set up HBMM bitmaps in your policy as Multi-use,  
which allows an HBMM bitmap to automatically be converted to a Mini-Copy  
write bitmap at the time of the loss of a shadowset member.
2) Boot each node by default as a satellite node of the other 2 nodes.  
This allows the booting node to boot from the present 2-member system disk  
shadowset instead of its out-of-date local copy, and then once it's up you  
could add its member to the system disk shadowset with a Mini-Copy  
operation.

Obviously in a full cluster reboot scenario you have to override the  
default and boot the very first node from its local system disk, but after  
that the other 2 nodes can boot as satellites.