The jig is up. The primary reason for updating VMS to 4.4 on Kim was to
see if the multi-disk volume set bug was fixed. It was, so DRA2 is going
to be combined with DRA1 into a single logical volume. The procedure for
doing this is to empty DRA2, re-initialise it, mount it /BIND'ed to DRA1
and restore the files. You will then see the directory trees that you
had on DRA1 and DRA2 merged into one tree. If there are duplicate files
on the two volumes or files with the same names (but different contents)
in the same place in duplicate directory trees, they'll probably get
screwed up. I suggest you rename the directories you have on DRA2 so they
don't match directories you have on DRA1 IF you don't want them merged.

When VMS adds a file to a multi-disk volume set, it puts the file on the
disk that has the most room. This allows us to combine the free space of
both drive 1 and 2 into one big pool, but also means we can't go back to
a single drive system. Files are allowed to overflow from one volume to
another should the free space on one disk get used up. Additional volumes
can be added at any time, so we could stick on another disk with no
difficulty later. In case you're worried about all your command files
breaking because they specifically point to files on drive 1 or 2, you
needn't worry. In a multi-disk volume set one may use the device name
of any of the disks in the set to reference the whole set. I.e. DRA1:
(or SYS$USERDISK:) and DRA2: may be used equally so no command files
should break.

I'll do the restore after you have notified me that you are done "fixing"
anything on DRA2.

ds