OpenVMS System Manager's Manual

Table 10-5 Sample Process Quotas for Efficient Backups

Process Quota	Suggested Value
WSQUOTA	16384
WSEXTENT	Greater than or equal to WSQUOTA
PGFLQUOTA	32768
FILLM	128
DIOLM	4096
ASTLM	4096
BIOLM	128
BYTLM	65536
ENQLM	256

Example

The following steps show the commands that you would use to run the Authorize utility and set process quotas for the SYSTEM account (if you plan to run backups from a different account, determine the process quotas for that account):

1. Determine the current quota values:

   $ SET DEFAULT SYS$SYSTEM
   $ RUN AUTHORIZE
   UAF> SHOW SYSTEM
   Username: SYSTEM                           Owner:  SYSTEM MANAGER 
   Account:  SYSTEM                           UIC:    [1,4] ([SYSTEM]) 
   CLI:      DCL                              Tables: DCLTABLES 
   Default:  SYS$SYSROOT:[SYSMGR] 
                                    . 
                                    . 
                                    . 
   Maxjobs:         0  Fillm:        40  Bytlm:        32768 
   Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 
   Maxdetach:       0  BIOlm:        18  JTquota:       1024 
   Prclm:          10  DIOlm:        18  WSdef:          256 
   Prio:            4  ASTlm:        24  WSquo:          512 
   Queprio:         0  TQElm:        20  WSextent:      2048 
   CPU:        (none)  Enqlm:       200  Pgflquo:      20480 
                                    . 
                                    . 
                                    . 
   UAF> EXIT
   %UAF-I-NOMODS, no modifications made to system authorization file 
   %UAF-I-NAFNOMODS, no modifications made to network authorization file 
   %UAF-I-RDBNOMODS, no modifications made to rights database 
   $
   

   
   In this example, SYSTEM has the following quotas:

   WSQUOTA	512
   WSEXTENT	2048
   PGFLQUOTA	20480
   FILLM	40
   DIOLM	18
   ASTLM	24
   BIOLM	18
   BYTLM	32768
   ENQLM	200

2. Using the System Management utility (SYSMAN), determine the value of the system parameters WSMAX and CHANNELCNT, as follows:

   $ RUN SYS$SYSTEM:SYSMAN
   SYSMAN> PARAMETERS SHOW WSMAX
   %SYSMAN-I-USEACTNOD, a USE ACTIVE has been defaulted on node DIEM 
   Node DIEM:   Parameters in use: ACTIVE 
   Parameter Name          Current   Default   Minimum   Maximum Unit  Dynamic 
   --------------          -------   -------   -------   ------- ----  ------- 
   WSMAX                      2600      1024        60    100000 Pages       
   SYSMAN> PARAMETERS SHOW CHANNELCNT
   Parameter Name          Current   Default   Minimum   Maximum Unit  Dynamic 
   --------------          -------   -------   -------   ------- ----  ------- 
   CHANNELCNT                 127       127        21     2047 Channels     
    
   SYSMAN> EXIT
   $ 
   

   
   In this case, the values for WSMAX and CHANNELCNT, as shown in the column marked Current, are 2600 and 127, respectively.
3. Compare the values for SYSTEM to the values in Table 10-4, and set the appropriate values:

   $ 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
   

4. Log out and then log in again so that these process quotas take effect.

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:

1. Determine the device name.
2. Allocate the device.
3. Initialize the volume (optional).
4. Mount the device (for disks only; BACKUP mounts tapes automatically).

These tasks are described in Chapter 8. This chapter describes specifically how these tasks relate to BACKUP. Note that all disk operations in this chapter also apply to diskettes.

10.8.1 Understanding Volume Initialization

Initializing a volume does the following:

• Formats it in the OpenVMS Files--11 format
• Assigns it an ANSI label
• Removes links to any existing files (effectively erasing them)
• Writes a tape expiration date and volume protection data to the volume header record of the tape

Caution

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:

• The volume is new and has not been formatted in the Files--11 format.
• You want to remove access to data stored on the volume.
• You want to change the volume label, expiration date, or volume protection data.
• The volume contains a non-ANSI or non-ISO label.

Table 10-6 show the three ways to initialize a volume.

Table 10-6 Methods of Volume Initialization

Method	For More Information
Before a backup operation with the DCL command INITIALIZE	Section 8.3
On the BACKUP command line with the /REWIND qualifier (for tapes only)	Section 10.8.1.2
On the BACKUP command line with the /INITIALIZE qualifier (for disks only)	Section 10.8.1.3

10.8.1.2 Initializing Tapes

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.

How to Perform This Task

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:

• If the tape volume has already been initialized with a label that is different from the label you specify on the BACKUP command line, BACKUP displays an error message about the label mismatch. For more information, see Section 10.12.
• If the tape is not expired, BACKUP displays the following error message:

  %INIT-F-FILNOTEXP, file is not expired 
  

  
  If you have either VOLPRO privilege or write access to the volume, or you are the owner of the volume, you can use the DCL command INITIALIZE/OVERRIDE=EXPIRATION to initialize the magnetic tape.
  You can also reenter the BACKUP command line using the /IGNORE=LABEL_PROCESSING qualifier (see the OpenVMS System Management Utilities Reference Manual).
• If the volume was previously initialized with the output save-set qualifiers /REWIND and /PROTECTION, you must either own the volume (your UIC matches the owner UIC of the volume) or have VOLPRO privilege.

Example

$ 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.

How to Perform This Task

The two ways to initialize a disk during a backup operation are:

• When you perform an image copy to disk, BACKUP automatically initializes the output disk, effectively erasing any existing files and volume-initialization data on the disk. To preserve volume-initialization data on the output disk, use the /NOINITIALIZE qualifier.
• When you create a sequential disk save set, BACKUP does not initialize the output volume (by default). You can, however, instruct BACKUP to initialize the output volume using the /INITIALIZE qualifier.

Examples

1. The following command shows how to initialize a disk on the BACKUP command line:

   $ BACKUP/IMAGE DUA1: DUA2:
   

   
   This command initializes DUA2: using the volume-initialization data from DUA1. BACKUP then copies the contents of DUA1: to DUA2:, effectively erasing any existing files on DUA2. Note that the files on DUA2: are stored contiguously, eliminating disk fragmentation.
2. The following command shows how to preserve volume-initialization data on the output disk during an image copy:

   $ BACKUP/IMAGE DUA1: DUA2:/NOINITIALIZE
   

   
   This command causes BACKUP to initialize DUA2:, preserving the initialization data on that volume. BACKUP then copies the contents of DUA1: to DUA2:, effectively erasing any existing files on DUA2.
3. These commands cause BACKUP to initialize DJA2:, effectively erasing any existing files:

   $ MOUNT/FOREIGN DJA2:
   %MOUNT-I-MOUNTED, USER1 mounted on _DJA2:
   $ BACKUP/IMAGE DUA1: DJA2:DAILY.SAV/INITIALIZE
   

   
   BACKUP then creates an image backup of DUA1: in the sequential disk save set DUA2:[000000]DAILY.SAV. If the save set exceeds the available disk space, BACKUP prompts for another volume. BACKUP initializes the new volume and extends the save set in the master file directory ([000000]) of the new volume. (For more information about save sets, see Section 10.5. For more information about the /INITIALIZE qualifier, see the OpenVMS System Management Utilities Reference Manual.)

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:

• If the save set will be written in standard Files--11 format, the target disk must be mounted as a Files--11 disk.
• If a save set will be written in sequential-disk format (for example, if the save set occupies more than one disk), the target disk must be mounted as a foreign device by specifying the command qualifier /FOREIGN to the DCL command MOUNT.

How to Perform This Task

1. Enter the SHOW DEVICES command in the following format to check whether the device is already mounted:

   SHOW DEVICES device-name 
   

2. Enter the MOUNT command in the following format:

   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.

Example

$ 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.

10.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.

How to Perform This Task

Enter the DISMOUNT command in the following format:

DISMOUNT  device-name 

Example

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.)

10.9.1 Requesting Operator Assistance

Note

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.

How to Perform This Task

Enter either the REQUEST/REPLY or the REQUEST/TO command:

• The /REPLY qualifier assigns your request a unique number to which the operator can respond.
• If your facility is very large, several operators might each have specific tasks. If this is the case, use the REQUEST/TO command, which allows you to send a message to a specific operator (identified by a keyword).

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:

• If a mount request fails and you specified /ASSIST, mount failure messages appear on the operator terminal (if OPCOM is enabled). The /ASSIST qualifier is the default for both the BACKUP and MOUNT commands.
• If you specified /NOASSIST, mount failure messages appear on your terminal instead of on the operator terminal.
• If you are on a workstation but forget to specify /NOASSIST, OPCOM (if OPCOM is running) requests that the operator load the next volume.

  
  If you have the OPER privilege, you can respond to the request by using another terminal window to enter the following commands:

  $ REPLY/ENABLE=TAPES
  $ REPLY/TO=identification-number "message text"
  

Examples

1. To request the operator to mount a tape, enter a command similar to the following :

   $ 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-1996 12:26:13.12. request 2 completed by operator OPA0
   $
   

   
   The /REPLY qualifier assigns your request a unique number (in this case, 2) to which the operator can respond. Note that you cannot enter any additional commands until the operator responds.
2. The following example shows you how to direct your request to a specific operator using the /TO qualifier:

   $ 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-1996 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.

How to Perform This Task

To list the contents of a BACKUP save set, do the following:

1. Insert the media containing the save set into the drive.
2. If the volume is a disk, mount the disk as described in Section 10.8.2 (BACKUP mounts tapes automatically).
3. Enter the BACKUP/LIST command in the format specified in the OpenVMS System Management Utilities Reference Manual. The /REWIND qualifier rewinds the tape to the beginning before searching for the save set. To list all the save sets on a volume, include the asterisk wildcard character (*) with the device specification.
   To list the contents of save sets does not require you to know the names of save sets on magnetic tape. Enter the device specification of the drive in which the tape is inserted with the BACKUP/LIST command. BACKUP reads the next save set it encounters on the magnetic tape and stops processing when it reaches the end of that save set. BACKUP does not automatically rewind to the beginning-of-tape marker unless you include the /REWIND qualifier in your command. Therefore, you can list the next save set (if one exists) by repeating the BACKUP/LIST command. If no more save sets exist on the tape, BACKUP issues the following error messages:

   %BACKUP-F-OPENIN, error opening MUA0:[000000].; as input 
   -SYSTEM-W-NOSUCHFILE, no such file 
   

Examples

1. To obtain save-set information about a magnetic tape save set named 2MAR1555.BCK in the drive MIA0:, enter the following command:

   $ BACKUP/LIST MIA0:2MAR1555.BCK/REWIND
   Listing of save set(s)
   Save set:          2MAR1555.BCK
   Written by:        POLYANNA 
   UIC:               [000200,000207]
   Date:              21-MAY-1996 09:36:14.68
   Command:           BACKUP/LOG [USER.SAVE] MIA0:2MAR555.BCK/REWIND/LABEL=WKY201
              
   Operating system:  OpenVMS Alpha Version 7.1
    
   BACKUP version:    7.1
   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-1996 14:10
   [USER.SAVE]LAST.DAT;1                     1  18-MAY-1996 14:11
   [USER.SAVE]THAT.DAT;1                     7  18-MAY-1996 14:10
   [USER.SAVE]THIS.DAT;2                     1  18-MAY-1996 13:44
   Total of 4 files, 10 blocks
   End of save set
   

2. The following command rewinds the tape to the beginning and lists all save sets on the volume MIA0:

   $ BACKUP/LIST MIA0:*.*/REWIND
   

3. The following command combines a list operation with a save operation to magnetic tape:

   $ BACKUP/LIST=MYBACK.DAT [PRAMS] MTA0:2MAR1555.BCK/LABEL=DLY201
   

   
   BACKUP verifies that the volume label is DLY201 and copies the contents of the directory [PRAMS] to a save set named 2MAR1555.BCK. The command qualifier LIST causes BACKUP to write save-set information to the file MYBACK.DAT as the save operation proceeds.

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 does the following:

• If you specified only one drive in the BACKUP command line and you are not using a tape loader or operator assistance, BACKUP prompts you to remove the tape that is in the drive and insert another one:

  %BACKUP-I-RESUME, resuming operation on volume 2
  %BACKUP-I-READYWRITE, mount volume DAILY02 on MUA0: for writing
  Respond with YES when ready:
  

  ---

  Note

  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 
  %MOUNT-I-OPRQST, Please mount volume DAILY02 in device MUA0: 
  BACKUP requests: Saveset DAILY.SAV, Volume number 02, write ENABLED 
  

  ---

  
  After you insert and load the second volume (or an operator fulfills the mount request), BACKUP continues writing data to the second volume.
• If you specified multiple drives on the command line, BACKUP continues writing data to the second volume, assuming the drive is loaded, is on line, and has the correct volume label. BACKUP unloads the first volume and displays the following message:

  %BACKUP-I-RESUME, resuming operation on volume 2
  

• If you are using a tape loader, BACKUP continues writing data to the tape in the next slot, assuming the tape loader has an adequate supply of correctly labeled tapes. BACKUP rewinds and unloads the first tape and displays the following message:

  %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:

• If you did not specify a label on the command line, BACKUP uses the first six characters of the save-set name to create a label for the first volume (unless you use the /EXACT_ORDER qualifier, in which case BACKUP preserves the volume label on the tape). For subsequent volumes, BACKUP uses the first four characters from the label of the first volume plus the number of the volume in the sequence. For example, suppose you are saving files that require three tapes and the save-set name is BACKUP. If you do not specify a label, the first tape is labeled BACKUP, the second BACK02, and the third BACK03.
• If you specified a single label on the command line using the /LABEL qualifier and it matches the label of the first volume, BACKUP labels subsequent volumes with the first four characters of the label from the first volume plus the number of the volume in the sequence. For example, suppose you are saving files that require three tapes and the first tape is labeled TAPE. The second tape gets the label TAPE02, and the third tape gets the label TAPE03.
• If you specified multiple labels on the command line using the /LABEL qualifier (without the /EXACT_ORDER qualifier), BACKUP uses the labels you specify. If the operation requires more labels than you specified, BACKUP uses the first four characters of the last volume label and the volume number of the tape.
• You can use the /EXACT_ORDER qualifier in conjunction with the /LABEL qualifier to specify the order in which you want BACKUP to use the labels. BACKUP continues the operation as long as the label of the tape in the drive matches the corresponding label on the command line. 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 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.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 does the following:

• Checks the volume protection information to ensure that you have the right to access the volume in the manner you requested.
• Checks the tape expiration date to prevent you from initializing a magnetic tape that has not yet expired.
• Compares the volume label specified in the BACKUP command line (either explicitly with the /LABEL qualifier or implicitly through the save-set name) to the volume label of the tape to prevent you from creating a save set on the wrong magnetic tape. BACKUP uses the following guidelines when processing tape labels:
  • If you specify a label that is longer than six characters, BACKUP truncates the label to six characters.
  • If the volume label is less than six characters long, BACKUP pads the volume label with the blank character to six characters.
  • The first four characters of the volume label either must match the first four characters of the label specified in the BACKUP command line exactly, or must end with one or more underscore characters. If the first four characters of the volume label end with one or more underscore characters, and the label specified in the command line matches the part of the volume label that appears before the underscore characters, BACKUP accepts the match. (For example, the volume label ABN_ matches the command line label ABN but does not match the command line label ABNE.)
  • If the fifth and sixth characters of the volume label are numbers between 0 and 9, BACKUP does not compare these characters with corresponding characters in the label specified in the BACKUP command line. Otherwise, the fifth and sixth characters in the volume label must exactly match the corresponding characters in the label specified in the BACKUP command line.

  6017P030.HTM
  OSSG Documentation
  22-NOV-1996 14:22:00.25

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal