Updated: 11 December 1998 |
OpenVMS System Manager's Manual
Previous | Contents | Index |
If you have a standalone workstation or easy access to disk and tape drives at your facility, you probably can mount and initialize your own volumes. At some sites, however, an operator performs these tasks. Using the services of an operator might be necessary because the drive you want to use is located remotely or because you do not have the necessary privileges to manipulate a volume.
To communicate with the operator at your site, consult the operator
about site-specific procedures. Depending on how your system is
customized, using the operator communication manager (OPCOM) might be
necessary. The OPCOM system process allows you to request assistance
from the operator and allows the operator to respond to your requests.
( Section 2.4 explains OPCOM.)
10.9.1 Requesting Operator Assistance
Please consult your operator about your site-specific procedures. Your site may not use OPCOM or may use it differently from the examples in this section. |
If you want the operator to mount a tape for you, use OPCOM to ask the operator to mount the tape.
Enter either the REQUEST/REPLY or the REQUEST/TO command:
If you request operator assistance and an operator is not available, you receive the following message:
%MOUNT-I-NOOPR, no operator available to service request |
This indicates that the operator has disabled the operator's terminal. To abort your request, press Ctrl/Z.
You can also use the /[NO]ASSIST qualifier with either the BACKUP or the MOUNT command:
$ REPLY/ENABLE=TAPES $ REPLY/TO=identification-number "message text" |
$ REQUEST/REPLY "Is anyone using drive MUA12?" %OPCOM-S-OPRNOTIF, operator notified, waiting...12:21:12.46 %OPCOM-S-OPREPLY, PLEASE DIRECT YOUR REQUEST TO THE TAPE OPERATOR 2-APR-1998 12:26:13.12. request 2 completed by operator OPA0 $ |
$ REQUEST/TO=TAPES "Is anyone using drive MUA12?" %OPCOM-S-OPRNOTIF, operator notified, waiting...12:40:11.32 %OPCOM-S-OPREPLY, I'M DONE GO AHEAD 2-APR-1998 12:45:26.18. request 5 completed by operator OPA0 $ |
BACKUP allows you to obtain information about save sets and the files in a save set. You can display this information at your terminal or send it to an output file.
Because BACKUP writes save sets in a format that only BACKUP can interpret, a list operation is the only way to determine the contents of a save set without restoring the save set. You can perform a list operation in conjunction with any other BACKUP operation.
By default, a save-set listing supplies information about files in the save set similar to the information supplied by the DCL command DIRECTORY/DATE/SIZE, including the actual number of blocks used for each file.
You can also perform a BACKUP list operation to list the contents of a BACKUP journal file. BACKUP journal files, which are created during a save operation by using the command qualifier /JOURNAL[=file-spec], contain on-disk records of BACKUP save operations and the file specifications of the files saved during each operation. Section 10.13.4 contains more information about creating and listing BACKUP journal files.
To list the contents of a BACKUP save set, perform the following actions:
%BACKUP-F-OPENIN, error opening MUA0:[000000].; as input -SYSTEM-W-NOSUCHFILE, no such file |
$ BACKUP/LIST MIA0:2MAR1555.BCK/REWIND Listing of save set(s) Save set: 2MAR1555.BCK Written by: POLYANNA UIC: [000200,000207] Date: 21-MAY-1998 09:36:14.68 Command: BACKUP/LOG [USER.SAVE] MIA0:2MAR555.BCK/REWIND/LABEL=WKY201 Operating system: OpenVMS Alpha Version 7.2 BACKUP version: 7.2 CPU ID register: 08000000 Node name: _SUZI:: Written on: _MIA0: Block size: 8192 Group size: 10 Buffer count: 3 [USER.SAVE]ANOTHER.DAT;1 1 18-MAY-1998 14:10 [USER.SAVE]LAST.DAT;1 1 18-MAY-1998 14:11 [USER.SAVE]THAT.DAT;1 7 18-MAY-1998 14:10 [USER.SAVE]THIS.DAT;2 1 18-MAY-1998 13:44 Total of 4 files, 10 blocks End of save set |
$ BACKUP/LIST MIA0:*.*/REWIND |
$ BACKUP/LIST=MYBACK.DAT [PRAMS] MTA0:2MAR1555.BCK/LABEL=DLY201 |
When you save data with BACKUP, the save set often spans more than one volume, creating a multivolume save set. When this occurs, BACKUP fits as much data as it can on the first volume, then dismounts it. Depending on whether you specified more than one drive in the BACKUP command line or if you are using a tape loader, BACKUP then performs the following actions:
%BACKUP-I-RESUME, resuming operation on volume 2 %BACKUP-I-READYWRITE, mount volume DAILY02 on MUA0: for writing Respond with YES when ready: |
If you are using OPCOM and the /ASSIST qualifier (the default), the following message appears on your terminal:
|
%BACKUP-I-RESUME, resuming operation on volume 2 |
%BACKUP-I-RESUME, resuming operation on volume 2 . . . |
In a multivolume save-set operation, BACKUP does not initialize the first volume (unless you use the /REWIND qualifier). BACKUP does initialize subsequent volumes. BACKUP determines the volume labels for subsequent volumes as follows:
As a safeguard against initializing or writing the wrong tape, BACKUP
compares the label that you specify on the command line to the label of
the tape in the drive. Section 10.12 describes how BACKUP processes
tape labels and handles a label mismatch.
10.11.2 MOUNT Messages When Backing Up Tapes
The MOUNT utility generates VOLINV messages on continuation tape volumes during backups when you use devices that have loaders or when the stackers or loaders become empty. The following example shows messages displayed:
%MOUNT-I-MOUNTED, ABCD03 mounted on _$4$MUA3: (HSC70) %BACKUP-I-RESUME, resuming operation on volume 4 %MOUNT-F-VOLINV, volume is not software enabled %BACKUP-I-READYWRITE, mount volume 4 on _$4$MUA3: for writing Enter "YES" when ready: yes %MOUNT-I-MOUNTED, ABCD04 mounted on _$4$MUA3: (HSC70) |
Once the devices are put back on line or the media is made ready, the
backup session continues or finishes as expected. This problem will be
addressed in a future release.
10.12 Understanding BACKUP Tape Label Processing
After mounting a tape, BACKUP processes information stored in the volume header record of the tape before writing to it. Specifically, BACKUP performs the following actions:
If the labels match, you have the proper protection, and the tape is expired, BACKUP performs the designated operation.
If you specify more than one label with the /LABEL qualifier and you do not specify the /EXACT_ORDER qualifier, the BACKUP operation succeeds if any of the labels you specify match the tape's volume label. For example, if the tape's volume label is MA1686, the BACKUP operation will succeed if you specify the following list of labels with the /LABEL qualifier:
/LABEL=(MA1684,MA1685,MA1686) |
If the volume labels do not match, BACKUP displays the following error message:
%MOUNT-I-MOUNTED, DKA0 mounted on _SODAK$MUA0: %BACKUP-W-MOUNTERR, volume 1 on _SODAK$MUA0 was not mounted because its label does not match the one requested %BACKUP-W-EXLABEER, volume label processing failed because volume MB1684 is out of order, Volume label MA1684 was expected specify option (QUIT, NEW tape, OVERWRITE tape, USE loaded tape) BACKUP> |
Depending on the option you specify, you can quit the backup operation (QUIT), dismount the old tape and mount a new one (NEW), overwrite the data on the tape (OVERWRITE), or USE the loaded tape.
If you specify more than one label with the /LABEL qualifier and you also specify the /EXACT_ORDER qualifier, BACKUP compares the label of the loaded tape with the first label that you specified with the /LABEL qualifier. If the labels match, BACKUP begins the operation. If the labels do not match, BACKUP prompts you with the previous message.
Assuming the volume labels of the tapes you use match the corresponding labels on the command line, BACKUP continues processing until it completes the operation or runs out of volume labels. If you do not specify enough labels on the command line to complete the operation or if the tape loaded does not have an ANSI label, BACKUP prompts you to enter a label for the tape in the drive.
If you use blank tapes or tapes that you intend to overwrite, use the /IGNORE=LABEL_PROCESSING qualifier. This suppresses the previous BACKUP message, which normally occurs if BACKUP encounters a non-ANSI-labeled tape during a save operation.
For more information about the /EXACT_ORDER, /IGNORE, and /LABEL
qualifiers, refer to the OpenVMS System Management Utilities Reference Manual.
10.13 Backing Up Files and Directories
This section explains copying files, backing up files and directories, comparing files, and creating and listing BACKUP journal files.
When you use the Backup utility with files, BACKUP processes relative version -0 as if it were 0, saving the most recent version instead of the earliest version of the file for processing. |
You can copy files using BACKUP. The copy function of the BACKUP command differs from the DCL command COPY because it preserves certain file information such as the version number, creation dates, revision dates, and protection codes (although, by default, the owner UIC of the copies is the UIC of the current process). Also, unlike the DCL command COPY, you can use BACKUP to copy entire directory trees, maintaining the directory structure.
To make identical disk-to-disk copies of files, use the following format:
BACKUP input-specifier output-specifier |
$ BACKUP EMPLOYEES.DAT USER1:[BATES.TEST]EMPLOYEES.DAT |
$ BACKUP USER1:[BATES...] USER2:[BATES...] |
$ BACKUP [LYKINS...]*.*;* [OWLCR...]*.*;* |
Disk-to-disk copy operations initiated using the /VERIFY qualifier might attempt to verify files that are not copied. For example, if an error prevents you from successfully copying a file from one disk to another location and you specified the /VERIFY qualifier for that operation, the system displays two error messages: one indicates that the file was not copied, and the other indicates that the file was not verified. |
One of the most common BACKUP operations is to save files to a save set. There are several types of save sets. For more information about save sets, see Section 10.5.
To back up files or directories, use the BACKUP command in the following format:
BACKUP input-specifier output-specifier [/SAVE_SET] [/LABEL=label] |
The input-specifier specifies the file you want to back up, and the output-specifier specifies the device and save-set name.
When you save data to disk, use the output save-set qualifier /SAVE_SET. If you do not specify /SAVE_SET, BACKUP copies files in standard file format rather than creating a BACKUP save set. When you save data to tape, you do not need to specify /SAVE_SET; BACKUP treats all magnetic tape files as save sets. Use the /LABEL qualifier to specify the label of the tape you are using.
$ ALLOCATE MUA0: TAPE1(1) %DCL-I-ALLOC, MUA0: allocated $ INITIALIZE TAPE1 DLY101(2) $ BACKUP/LOG EMPLOYEES.DAT MUA0:EMPL_MAY91.BCK/LABEL=DLY101(3) %MOUNT-I-MOUNTED, BACKUP mounted on _MUA0: BACKUP-S-COPIED, copied DUA0:[SCHULT]EMPLOYEES.DAT;32 $ |
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6017PRO_045.HTML
|