Document revision date: 15 July 2002 | |
Previous | Contents | Index |
$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY SYSTEM/WSQUOTA=2600 UAF> MODIFY SYSTEM/WSEXTENT=2600 UAF> MODIFY SYSTEM/DIOLM=4096 UAF> MODIFY SYSTEM/ASTLM=4096 UAF> MODIFY SYSTEM/BIOLM=40 UAF> MODIFY SYSTEM/BYTLM=34816 UAF> EXIT |
During the course of your backup operations, you will use both disk and tape volumes. The steps you normally perform before using a volume in a backup operation are:
These tasks are described in Chapter 9. This chapter describes
specifically how these tasks relate to BACKUP. Note that all disk
operations in this chapter also apply to diskettes.
11.8.1 Understanding Volume Initialization
Initializing a volume completes the following actions:
Initializing a volume removes links to existing files on the volume, effectively erasing the files. Do not initialize a volume that contains data you want to keep. |
You must initialize a volume for use with BACKUP if any of the following conditions exist:
Table 11-6 show the three ways to initialize a volume.
Method | For More Information |
---|---|
Before a backup operation with the DCL command INITIALIZE | Section 9.3 |
On the BACKUP command line with the /REWIND qualifier (for tapes only) | Section 11.8.1.2 |
On the BACKUP command line with the /INITIALIZE qualifier (for disks only) | Section 11.8.1.3 |
Instead of using the INITIALIZE command and then performing a backup operation, you can initialize a tape and perform a backup operation by entering one BACKUP command.
To initialize a tape volume on the BACKUP command line, add the /REWIND and /LABEL qualifiers to the output specifier. The /REWIND qualifier rewinds and initializes the volume. The /LABEL qualifier allows you to specify the volume label.
Magnetic tape volume labels can contain a maximum of six characters. You can use any ANSI "a" character in a magnetic tape volume label. The ANSI "a" characters include numbers, uppercase letters, and any of the following nonalphanumeric characters:
! " % ' ( ) * + , _ . / : ; < = > ? |
If you use any nonalphanumeric characters, you must enclose the volume label with quotation marks.
Label your magnetic tapes according to the data contained on the tapes. The following table presents some suggestions for labeling tapes:
Label | Type of Backup | Expiration Date |
---|---|---|
DLY101 | Daily, group 1, volume number 1 | Expires in 7 days |
DLY102 | Daily, group 1, volume number 2 | Expires in 7 days |
WKY101 | Weekly, group 1, volume number 1 | Expires in 4 weeks |
WKY201 | Weekly, group 2, volume number 1 | Expires in 4 weeks |
MTH101 | Monthly, group 1, volume number 1 | Expires in 12 months |
YRY101 | Yearly, group 1, volume number 1 | Expires in 5 years |
Note that:
%INIT-F-FILNOTEXP, file is not expired |
$ BACKUP [ACCOUNTS.JUNE] MUA0:JUNE.BCK/REWIND/LABEL=MTH101 |
Instead of using the INITIALIZE command and then performing a backup operation, you can initialize a disk and perform a backup operation by entering one BACKUP command.
The two ways to initialize a disk during a backup operation are:
$ BACKUP/IMAGE DUA1: DUA2: |
$ BACKUP/IMAGE DUA1: DUA2:/NOINITIALIZE |
$ MOUNT/FOREIGN DJA2: %MOUNT-I-MOUNTED, USER1 mounted on _DJA2: $ BACKUP/IMAGE DUA1: DJA2:DAILY.SAV/INITIALIZE |
Mounting a volume makes it available to the system. BACKUP automatically mounts tapes when you use them for a backup operation. Most disks on your system are mounted at system startup. This section describes how to explicitly mount volumes.
If you are planning to write a save set to a disk, decide whether the save set will be written in standard Files--11 format or in sequential-disk format:
SHOW DEVICES device-name |
MOUNT [/FOREIGN] device-name [volume-label] [logical-name] |
where:
device-name | is the name of the drive that holds the volume you want to mount. |
volume-label | is the alphanumeric identification you assigned to the volume with the INITIALIZE command. For disk volumes, labels can have a maximum of 12 characters; for magnetic tape volumes, labels can have a maximum of 6 characters. You do not need to add this parameter if you are mounting the volume with the /FOREIGN qualifier. |
logical-name | is an optional 1- to 255-character alphanumeric specification that you want to associate with the volume. |
$ SHOW DEVICE MU Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DAD$MUA6: Online 0 MOM$MUA6: Online 0 FRED$MUA6: Online 0 $ MOUNT/FOREIGN FRED$MUA6: TEST DRIVE1 %MOUNT-I-MOUNTED, TEST mounted on _FRED$MUA6: |
This command mounts the tape in FRED$MUA6: and assigns it the logical
name DRIVE1.
11.8.3 Dismounting a Volume
BACKUP does not dismount the last volume of a backup operation (unless you use the /RELEASE_TAPE qualifier). When you finish using a volume, you should dismount it.
Enter the DISMOUNT command in the following format:
DISMOUNT device-name |
The following command dismounts a tape in drive MUB6:
$ DISMOUNT MUB6: |
This command dismounts and unloads the tape in MUB6. After you dismount and unload the volume, you can remove it from the drive. To dismount the tape but not unload it, enter the following command:
$ DISMOUNT/NOUNLOAD MUB6: |
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.)
11.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-2000 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-2000 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 11.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-2000 09:36:14.68 Command: BACKUP/LOG [USER.SAVE] MIA0:2MAR555.BCK/REWIND/LABEL=WKY201 Operating system: OpenVMS Alpha Version 7.3 BACKUP version: 7.3 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-2000 14:10 [USER.SAVE]LAST.DAT;1 1 18-MAY-2000 14:11 [USER.SAVE]THAT.DAT;1 7 18-MAY-2000 14:10 [USER.SAVE]THIS.DAT;2 1 18-MAY-2000 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 . . . |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6017PRO_047.HTML |