 |
The Question is:
I am trying to build a Disaster Recovery system, with slightly different
architecture than the "production" cluster.
Since I cannot build the exact duplicate of the production cluster, I am using
BIND sets to give me enough room on the DRS to build the disks. In this, I am
now trying to do an image recovery to each set of Bind disks. I cannot get
the commands to do th
is to work. Here are the commands I entered for my first disk image recovery:
Ths bind set consists of three disks, DKD101,DKD105, DKD106. I mounted them
all $mount/for for each of the three disks, then execute the following command:
$backup/image tape:raid101.bck dkd101:,dkd105,dkd106.
The backup seems to be running, but it is actually do nothing at all. No error
message, and no response from the process. I have tried to STOP the process,
but I can't get the process to work or to stop. It hangs up with no messages
what so ever.
What am I doing wrong???
The Answer is :
There are various operations which are not supported with bound
volume sets, such as booting OpenVMS from a bound-volume set.
OpenVMS typically expects to see a MOUNT/BIND command used to bring
the bound-volume set on-line, and BACKUP/IMAGE remembers the number
of members within the source bound volume set when restoring the data.
In your case, the BACKUP command specified should operate if there
were an equal number of volumes in the source volume set.
For most other disk operations involving bound volume sets, only the
first (root) volume of the bound volume set should be referenced.
BACKUP can be an exception to this, see the BACKUP/IMAGE/VOLUME
and other related per-volume mechanisms.
Because BACKUP/IMAGE preserves the file identification values (FIDs),
you cannot attempt to write more data to the volume than it can support;
BACKUP would have to change the FID to relocate the file to a volume
with storage, once the first n volumes fill -- where n is the number
of volumes in the source bound volume set, and quite possibly 1.
A FID contains -- among various and sundry details -- the volume
number on which the file resides within a bound volume set and, as
stated, BACKUP/IMAGE explicitly preserves these FIDs.
To do what you want here and transfer data from larger volumes to bound
volume sets and particularly where the first volume of the bound volume
set is smaller than amount of input file data, you will likely end up
using COPY operations or BACKUP non-/IMAGE operations (file-based
operations, as differentiated from volume-based operations) to load
the volume.
Given increases in disk capacities and decreases in costs, the OpenVMS
Wizard generally discourages continued use of bound-volume sets.
|
|
|
|
|
