[Info-vax] Shadow Volume Copy

[Bob Gezelter]

On Mar 25, 5:54 am, Ramon Jimenez <rjime... at ford.com> wrote:
> We have a shadow logical disk, with two members.
>
> They want to copy the physical files which form the shadow to another
> machine.
>
> I'm trying to create  DCL with this commands
>
>  $  dismount lda1:
>  $!
>  $! copy file
>  $!
>  $  copy dkb0:[000000]vd1.dsk dkb1:[BACKUP]
>  $!
>  $! Mount disk again
>  $  mou/sys/noassi dsa0: /shadow=($1$lda1:,$1$lda2:) shadowvol vds
> $disk
>  $!
>  $!
>  $  dismount lda2:
>  $!
>  $! copy file
>  $!
>  $  copy dkb1:[000000]vd2.dsk dkb1:[BACKUP]
>  $!
>  $! Mount disk again
>  $  mou/sys/noassi dsa0: /shadow=($1$lda1:,$1$lda2:) shadowvol vds
> $disk
>
> When I ran the commands manually one bye it works
> When I put them in the DCL, dismounts and copies the first file and I
> got this message
>
>    %DISM-W-CANNOTDMT, LDA2: cannot be dismounted
>    %DISM-F-SRCMEM, only source member of shadow set cannot be
> dismounted
>
> I suppose is because it is still mounting the previous one. however it
> copies both files.
>
> How can I do that DCL wait for the finish of the first mount operation
> before starting the second dismount?
>
> Could be the files copied be valid although the volume has not be
> dismounted?
>
> Thanks
> Ramon

Ramon,

The first step is to see precisely what is happening with a SHOW
DEVICE/FULL on DSA0 to show the state of the shadow set BEFORE the
second MOUNT.

Two observations:

1) One can check the details of volume status by using the F$GETDVI
lexical function. There are a wide variety of items that can be
retrieved, including items
particular to shadowing (see the SHDW parameters). I recommend reading
the documentation in the DCL Command Dictionary for more details.

2) Why do things this way? Why not just join a THIRD member to the
shadow set, allow it to get completely up to date, then disconnect it
and move the resulting file. Once the third member has been created,
disconnect it, mount it privately and create a new second member from
it. Once it has been mounted privately, the Volume name can be changed
with the SET VOLUME command.

- Bob Gezelter, http://www.rlgsc.com