Document revision date: 15 July 2002 | |
Previous | Contents | Index |
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 11.12 describes how BACKUP processes
tape labels and handles a label mismatch.
11.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.
11.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.
11.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 11.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 $ |
$ BACKUP [LYKINS...] TAPE:NOV13SAVE.BCK/LABEL=NOV13 |
$ BACKUP _From: DUA0:[MGR]EMPLOYEES.DAT,USER1:[RECORDS]DOOHAN.DAT,EVANS.DAT _To: MUA1:MONTHLY_AUG.BCK/LABEL=TAPE1 |
$ BACKUP _From: DUA0:[000000]*.* _To: MTA1:BACKUP.BCK,MTA2: |
$ BACKUP STRATCOL1.DAT DUA1:STRATDAT1.BCK/SAVE_SET |
remote_nodename"username password"::device_name:[directory] |
For example:
$ BACKUP From: STRATCOL1.DAT To: NIMBL"ROGERS SANFRANCISCO"::WORK1:[ROGERS]STRATDAT1.BCK/SAVE_SET |
$ MOUNT/FOREIGN DUA0: $ BACKUP [] DUA0:NOV12SAVE.BCK/SAVE_SET |
$ BACKUP [REPORTS...] MIA11:REPORT.BCK/REWIND/IGNORE=LABEL_PROCESSING |
$ MOUNT DUA1: PAYROLL %MOUNT-I-MOUNTED, PAYROLL mounted on _DUA1: $ MOUNT DUA21: DISK21 %MOUNT-I-MOUNTED, DISK21 mounted on _DUA21: $ BACKUP From: DUA1:[PAYROLL] To: DUA21:[PAYROLL_BACKUPS]PAY22MAY2000.SAV/SAVE_SET |
$ MOUNT DUA1: PAYROLL %MOUNT-I-MOUNTED, PAYROLL mounted on _DUA1: $ MOUNT/FOREIGN DJA21: %MOUNT-I-MOUNTED, WEEKLY mounted on _DJA21: $ BACKUP From: DUA1:[PAYROLL] To: DJA21:[PAYROLL_BACKUPS]PAY22MAY2000.SAV/SAVE_SET |
Prior to OpenVMS Version 7.2, 32 levels of directories were supported. Beginning with OpenVMS Version 7.2 on VAX and Alpha systems, the number of levels of directories can be as high as RMS allows; for OpenVMS Version 7.2 and later, that number is 255 levels. |
A BACKUP compare operation compares a save set with disk files or compares disk files with other disk files. Perform a compare operation to check the integrity of a file or volume after a copy, save, or restore operation. For example, you can use the compare operation to compare a save set with original files or to compare files or volumes copied using BACKUP with original files.
Because BACKUP processes files by blocks, comparing files not produced by BACKUP is likely to cause mismatch errors in files that are apparently identical. |
The two ways to perform a compare operation are:
%BACKUP-I-STARTVERIFY, starting verification pass |
$ BACKUP/COMPARE MTA0:2MAR1555.BCK [LYKINS] |
$ BACKUP/COMPARE UPLIFT.EXE;3 UPLIFT.EXE;4 %BACKUP-E-VERIFYERR, verification error for block 16 of WRKD$:[LYKINS]UPLIFT.EXE;4 |
$ BACKUP/IMAGE/COMPARE DBA1: DBA2: |
$ MOUNT/FOREIGN DBA2: $ BACKUP/PHYSICAL/COMPARE MIA0:PHYSBACK.BCK DBA2: |
$ BACKUP/VERIFY/LOG FRED.DAT [FRIENDS]OLDFRED.DAT %BACKUP-S-CREATED, created DISK$:[FRIENDS]OLDFRED.DAT;3 %BACKUP-S-COMPARED, compared DISK$:[FRIENDS]OLDFRED.DAT;3 |
To keep a record of BACKUP operations, create a journal file. A BACKUP journal file contains records of BACKUP save operations and the file specifications of the files saved during each operation.
To create a journal file, use the command qualifier /JOURNAL=[file-spec] in a BACKUP save operation.
To list the contents of a BACKUP journal file, enter a command in the following format:
BACKUP/LIST[=file-spec]/JOURNAL[=file-spec] |
You cannot specify an input or output specifier with a BACKUP/LIST/JOURNAL command. If you omit the file specification from the command qualifier /LIST, BACKUP directs the output to your terminal; if you omit the file specification from the command qualifier /JOURNAL, the journal file receives the default BACKUP journal file name (SYS$DISK:[]BACKUP.BJL).
For more information about creating and listing BACKUP journal files, refer to the description of the /JOURNAL qualifier in the OpenVMS System Management Utilities Reference Manual.
This example shows how to create a BACKUP journal file and list the contents of the BACKUP journal file:
$ BACKUP/JOURNAL/LOG/IMAGE DRA2: MIA0:3OCT.FUL %BACKUP-S-COPIED, copied DRA2:[COLLINS]ALPHA.DAT;4 %BACKUP-S-COPIED, copied DRA2:[COLLINS]EDTINI.EDT;5 . . . %BACKUP-I-RESUME, resuming operation on volume 2 %BACKUP-I-READYWRITE, mount volume 2 on _MIA0: for writing Press return when ready: [Return] %BACKUP-S-COPIED, copied DRA2:[LANE]MAIL.MAI;1 %BACKUP-S-COPIED, copied DRA2:[LANE]MEMO.RNO;5 . . . $ BACKUP/JOURNAL/LIST Listing of BACKUP journal Journal file _DB2:[SYSMGR]BACKUP.BJL;1 on 3-OCT-2000 00:40:56.36 Save set 3OCT.FUL created on 3-OCT-2000 00:40:56.36 Volume number 1, volume label 3OCT01 [COLLINS]ALPHA.DAT;4 [COLLINS]EDTINI.EDT;5 [COLLINS]LOGIN.COM;46 [COLLINS]LOGIN.COM;45 [COLLINS]MAIL.MAI;1 [COLLINS]MAR.DIR;1 [COLLINS.MAR]GETJPI.EXE;9 [COLLINS.MAR]GETJPI.LIS;14 . . [LANE]LES.MAI;1 . . Save set 3OCT.FUL created on 3-OCT-2000 00:40:56.36 Volume number 2, volume label 3OCT02 [LANE]MAIL.MAI;1 [LANE]MEMO.RNO;5 [LANE]MEMO.RNO;4 . . [WALTERS.VI]KD.RNO;52 End of BACKUP journal |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6017PRO_048.HTML |