[Info-vax] (DIS)MOUNT/POLICY=MINICOPY

[Phillip Helbig---undress to reply]

In article <4d5860ec$1 at ns.langstoeger.at>, peter at langstoeger.at (Peter
'EPLAN' LANGSTOEGER) writes: 

> In article <ij8sfu$1ir$3 at online.de>, helbig at astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) writes:
> >I regularly use the minicopy feature to speed up the copy after a node 
> >hosting one of the members has been down for planned maintenance etc.  
> >Now, I want to physically move some disks.  If I dismount a member of a 
> >shadow set then physically remove it and connect it to another node such 
> >that it gets a different allocation class, SCSI address etc then mount 
> >it back into the shadow set, should I expect the minicopy to work?
> 
> I personally don't expect it (though I have no real experience).

It worked!  Apparently only the "volume shadowing generation number" is 
compared.  This is quite useful, as it makes moving physical disks about 
very painless.  (As I expected if it would work at all, it worked when 
the member dismounted was directly connected to an ALPHA and the one 
which remained mounted was directly connected to a VAX; the important 
thing is that the MOUNT and DISMOUNT commands get issued from an ALPHA.)

> AFAIK, you could DISMOUNT more than one disk at the same time with MINICOPY
> so the Bitmaps must have the name of the dismounted disks associated and so
> you can't [easily] change the name of the device then...

Apparently not.