1.$ BACKUP
_From: DBA1:[000000...]
_To: MTA0:13NOVBAK.BCK,MTA1:/LABEL=(DLY101,DLY102)
This BACKUP command saves the entire contents of the disk
DBA1 onto a multivolume tape save set. This command does not
initialize the first tape in the save set, but does initialize
subsequent tapes. The first tape in the save set must be
labeled DLY101 and the second tape in the save set must be
labeled DLY102.
2.$ BACKUP [PLI.WORK]/SINCE=YESTERDAY/MODIFIED [PLI.SAV]
This BACKUP command copies selected files in the directory
[PLI.WORK] to the directory [PLI.SAV]. BACKUP processes only
those files that have been modified since 24 hours preceding
midnight last night. Note that the /MODIFIED qualifier is
not required, as its action is the default when the /SINCE
qualifier is specified.
3.$ BACKUP DBA2:[PLI.WORK]*.*; DBA3:[SAVE]23MAR82.BCK/SAVE_SET
This BACKUP command saves the highest version of each file in
directory [PLI.WORK] to a disk save set on DBA3. The /SAVE_
SET qualifier is required because the output save set is on a
Files-11 disk.
4.$ BACKUP/PHYSICAL DYA0: DYA1:
This BACKUP command copies the entire RX02 floppy disk mounted
on device DYA0 to the RX02 floppy disk mounted on device
DYA1. Both devices must have been mounted with the DCL command
MOUNT/FOREIGN.
5.$ BACKUP
_From: DB1:[SCHED]*.*
_To: DENVER::DBA2:[SAVE]SCH.BCK/SAVE_SET
This BACKUP command saves all files in the directory SCHED
on disk DB1 at the local node to the network save set SCH.BCK
at remote node DENVER. The /SAVE_SET qualifier is required to
identify the output specifier as a save set on a Files-11 disk.
6.$ BACKUP/LIST DENVER::DBA2:[SAVE]SCH.BCK/SAVE_SET
This BACKUP command lists the BACKUP summary information,
the original BACKUP command used, and the file name, size,
and creation date for each file in the save set created in
the previous example. The /SAVE_SET qualifier is required
to identify the input specifier as a save set on a Files-11
device.
7.$ BACKUP MTA0:NOV2SAVE.BCK/REWIND/SELECT=[USER...] [USER...]
This command restores files from the magnetic tape save set
named NOV2SAVE.BCK to the directory tree from which they
were saved (the [USER] directory tree). The /REWIND qualifier
directs BACKUP to rewind the tape to the beginning-of-tape
before beginning the restore operation.
8.$ BACKUP WORK$:[TESTFILES...]*.*;* MUA0:TEST.SAV -
_$ /MEDIA_FORMAT=COMPACTION /REWIND
This command saves all files in the directory [TESTFILES] and
its subdirectories to a save set named TEST.SAV using a TA90E
tape drive. The /MEDIA_FORMAT=COMPACTION qualifier specifies
that the tape drive automatically compacts and blocks together
data records on the tape.
9.$ BACKUP/IMAGE/RECORD/VERIFY/NOASSIST
_From: DKA100:
_To: MKB100:MAR11.SAV/LABEL=(TAPE1,TAPE2,TAPE3)/EXACT_ORDER
This example uses the /EXACT_ORDER qualifier to specify the
exact order of labels for the BACKUP operation. Note that
if you specify the /ASSIST qualifier, BACKUP would display
messages on the operator terminal. BACKUP performs the
following tasks:
a. Compares the volume label of the tape in MKB100: with
the first label that you specified on the command line
(TAPE1). If the labels match exactly, BACKUP begins the
save operation. If the labels do not match or if the tape
does not have an ANSI label, BACKUP displays the following
message:
%BACKUP-W-MOUNTERR, volume 1 on MKB100: was not mounted because
its label does not match the one requested
%BACKUP-W-EXLABEER, volume label processing failed because
volume TAPE4 is out of order, Volume label TAPE1 was expected
specify option (QUIT, NEW tape, OVERWRITE tape, USE loaded tape)
BACKUP> OVERWRITE
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 label and the data on the tape
(OVERWRITE), or write the data to the tape using the loaded
tape's label (USE).
b. When the operation fills the first tape, it displays the
following message:
%BACKUP-I-RESUME, resuming operation on volume 2
%BACKUP-I-READYWRITE, mount volume TAPE2 on MKB100: for writing
Respond with YES when ready:
c. When you load the second tape and enter YES, BACKUP compares
the label of the second tape with the second label you
specified on the command line (TAPE2) just as it did in
step 1a.
d. Assuming the volume labels match, 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, BACKUP prompts you
to enter a label for the tape in the drive as follows:
%BACKUP-W-MOUNTERR, volume 4 on MKB100: was not mounted because
the label was not specified
specify EXACT_ORDER label (up to 6 characters)
BACKUP>
BACKUP then compares the label on the tape with label you
specify as described previously.
10$ BACKUP/IMAGE/RECORD/VERIFY/NOASSIST
_From: DKA100:[TEST]
_To: MKB100:MAR11.SAV/EXACT_ORDER
Because this example does not use the /LABEL qualifier, BACKUP
uses the existing label on the tape. If the tape does not
have an ANSI label, and it is the first tape in the operation,
BACKUP displays the following error message:
%BACKUP-F-NOTANSI, tape is not valid ANSI format
If the tape does not have an ANSI label, and is not the first
tape in the operation, BACKUP displays the following error
message prompting you to specify a label:
%BACKUP-W-MOUNTERR, volume 2 on MKB100: was not mounted because
the label was not specified
specify EXACT_ORDER label (up to 6 characters)
BACKUP>
NOTE
BACKUP checks to make sure you specify a valid label.
If the label is not valid (for example, longer than six
characters), BACKUP displays an error message. In previous
versions of the OpenVMS operating system, BACKUP truncated
long volume labels.
Additional Information:
explode
extract