[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

HP OpenVMS System Management Utilities Reference Manual

/EXACT_ORDER

Output Save-Set Qualifier
Depending on the other qualifiers you specify on the command line, the /EXACT_ORDER qualifier allows you to perform the following actions:

Specify the exact order of tape volume labels that you want to use in a BACKUP operation.
Preserve the existing volume label on a tape.
Prevent previous volumes of a multivolume save operation from being overwritten.

Format

input-specifier output-save-set-spec/EXACT_ORDER

Description

The /EXACT_ORDER qualifier allows you to perform the following actions:
Specify the exact order of tape volume labels that you want to use in a BACKUP operation. You must use the /LABEL=(label1,label2,...) qualifier to specify the order of 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.
Preserve the existing volume label on a tape. If you do not use the /LABEL qualifier on the command line and the tape has an ANSI label, BACKUP uses the existing label.
Prevent previous volumes of a multivolume save operation from being overwritten. BACKUP keeps track of the volume labels you have already used in the operation. If you accidently mount one of the previous volumes, BACKUP displays the following error message:
%BACKUP-W-MOUNTERR, volume 1 on MKB100: was not mounted because its label does not match the one requested Volume with label TAPE1 was already used in this save operation. Specify option (QUIT or NEW tape) BACKUP>
Note the following restrictions when you use the /EXACT_ORDER output qualifier:
If you use the /EXACT_ORDER qualifier, you cannot specify a label longer than six characters on the command line. If you specify a label longer than six characters, BACKUP displays the following error message:
%BACKUP-F-INVQUAVAL, value 'label_name' invalid for /LABEL qualifier
You cannot use the /IGNORE=LABEL_PROCESSING qualifier with the /EXACT_ORDER qualifier.
If you use the /LABEL qualifier with the /EXACT_ORDER qualifier, you cannot specify duplicate labels.
The default is /NOEXACT_ORDER.

Examples

#1
$ 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 actions:
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).
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:
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.
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.

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

/EXCLUDE

Input File-Selection Qualifier
Excludes files that otherwise meet the selection criteria for a save or copy operation. The excluded files are not processed.

Format

input-specifier/EXCLUDE=(file-spec[,...]) output-specifier

Description

If you specify more than one file, separate the file specifications with commas and enclose the list in parentheses. Do not use a device specification when defining the files to be excluded. You can use most standard wildcard characters, but you cannot use wildcard characters denoting latest versions of files (;) or relative versions of files (;-n).
Note that BACKUP does not apply temporary file specification defaults within the list. Each file specification independently takes its defaults from the file specification [000000...]*.*;*.
If you specify directory files (files with the file type .DIR), your command is processed but the directory files are not excluded (they are processed). BACKUP uses directory files to facilitate incremental restore operations.
You cannot use the /EXCLUDE qualifier in image restore operations.

Example


$ BACKUP _From: DRA2:[CONTRACTS]/BEFORE=TODAY/EXCLUDE=(.OBJ,.MAI) _To: MFA0:CONTRACT.BCK/LABEL=DLY102

All files in the directory [CONTRACTS] that have a modification date prior to today (the current day, month, and year at 00:00:00.0 o'clock) are saved to the save set CONTRACT.BCK on drive MFA0, except for those with a file type of .OBJ or .MAI.

/EXPIRED

Input File-Selection Qualifier
Selects files according to the value of the expiration date field in each file header record.

Format

input-specifier/BEFORE=time /EXPIRED output-specifier
input-specifier/SINCE=time /EXPIRED output-specifier

Description

You must use the input file-selection qualifier /BEFORE or /SINCE with /EXPIRED. The date and time you specify to /BEFORE or /SINCE determines which files are processed.
You cannot use /EXPIRED with the input file-selection qualifiers /BACKUP, /MODIFIED, or /CREATED.

Example


$ BACKUP [CONTRACTS]/BEFORE=TOMORROW/EXPIRED MTA1:30DEC.BCK/LABEL=WK04

This command saves all files in the directory [CONTRACTS] that have an expiration date prior to tomorrow (24 hours after midnight last night) to a save set named 30DEC.BCK.

/FAST

Command Qualifier
Processes the input specifier using a fast file scan to reduce processing time. The input specifier must be a Files--11 disk.

Format

/FAST input-specifier output-specifier

Description

The fast file scan reads the index file on the Files--11 disk specified by the input specifier and creates a table of files that match the qualifiers you specified.
When you use the /FAST qualifier to save a disk, ALIAS directory trees are not processed. Only the primary files that the ALIAS points to are saved. Depending on the number of ALIAS directory specifications there are on the disk, this may increase performance by reducing the number of files BACKUP checks for processing. A message is displayed for each ALIAS directory or file that is not processed.
To perform a fast file scan, you need write access to the INDEXF.SYS file on the input medium, or the input medium must be write-locked. This requirement is necessary because BACKUP opens the index file to synchronize with the file system, whether or not any update is made.
A fast file scan is most useful when the input specifier includes most of the files on the volume, and file-selection qualifiers (such as those that pertain to date or owner) specify a relatively small set of the files named. Because image operations implicitly use the fast file scan, the /FAST qualifier is ignored if used with the command qualifier /IMAGE.
You cannot use /FAST in restore operations.

Example


$ BACKUP/FAST _From: DBA1:[*...]/MODIFIED/SINCE=TODAY _To: MTA0:13NOVBAK.BCK,MTA1:/LABEL=WK201

In this example, all files on the disk DBA1 that have been modified today are saved to a multireel tape save set named 13NOVBAK.BCK. The /FAST qualifier is used to reduce processing time.

/FILES_SELECTED

Input File-Selection Qualifier
Specifies a file that contains a list of the files that will be selected when a save set is restored.

Format

input-specifier /FILES_SELECTED=file-spec output-specifier

Description

The /FILES_SELECTED qualifier allows you to specify a file that contains a list of the files that are to be selected when a save set is restored. You can use this qualifier in place of the /SELECT qualifier to select files to restore from a save set.
Do not use a device specification when you list the files to be selected. In the list of files, enter one OpenVMS file specification per line. You can use most standard wildcard characters, but you cannot use wildcard characters denoting the latest version of files (;) and relative versions of files (;-n).

Example


$ BACKUP INFO.BCK/SAVE_SET/FILES_SELECTED=RFILE.DAT []

The command in this example selects the files in RFILE.DAT and restores them to the current default directory. The RFILE.DAT file contains the following entries:
[INFO]RESTORE.COM [PAYROLL]BADGE.DAT EMPLOYEE.DAT

/FULL

Command Qualifier
Lists the file information produced by the command qualifier /LIST in the format provided by the DCL command DIRECTORY/FULL.

Format

/LIST/FULL input-specifier [output-specifier]

Description

The /FULL qualifier is valid only with the command qualifier /LIST.
If you do not specify /FULL with /LIST, the /LIST qualifier uses the default command qualifier /BRIEF and lists only the file specification, size, and creation date of each file. When you specify /FULL, the list includes more information from the file header records, such as the BACKUP date, date of last modification, number of blocks allocated to the file, file protection and organization, and record attributes.

Example

$ BACKUP/LIST/FULL MTA1:ROCK.BCK
Listing of save set(s)
Save set:          ROCK.BCK
Written by:        RINGO
UIC:               [000200,000300]
Date:              20-AUG-2002 15:39:38.89
Command:           BACKUP [.STONES] MTA0:ROCK.BCK/LABEL=BACKUP

Operating system:  OpenVMS Alpha Version V7.3-1

BACKUP version:    V7.3-1
CPU ID register:   08000000
Node name:         _SUZI::
Written on:        _MTA0:
Block size:        8192
Group size:        10
Buffer count:      30

[RINGO.STONES]GRAPHITE.DAT;1
                  Size:       1/1         Created: 18-AUG-2002 14:10
                  Owner: [000200,000200]  Revised: 18-AUG-2002 14:10 (2)
                  File ID: (91,7,1)       Expires: [None specified]
                                          Backup:  [No backup done]
  File protection:    System:RWED, Owner:RWED, Group:RE, World:
  File organization:  Sequential
  File attributes:    Allocation = 1, Extend = 0
                      Global Buffer Count = 0
  Record format:      Variable length, maximum 255 bytes
  Record attributes:  Carriage return

[RINGO.STONES]GRANITE.DAT;1
                      Size:    1/1        Created: 18-AUG-2002 14:11
                      Owner: [000200,000200]  Revised: 18-AUG-2002 14:11 (2)
                      File ID: (92,9,1)       Expires: [None specified]
                                              Backup:  [No backup done]
  File protection:    System:RWED, Owner:RWED, Group:RE, World:
  File organization:  Sequential
  File attributes:    Allocation = 1, Extend = 0
                      Global Buffer Count = 0
  Record format:      Variable length, maximum 255 bytes
  Record attributes:  Carriage return
.
.
.
Total of 4 files, 16 blocks
End of save set

The command in this example lists the files in save set MTA1:ROCK.BCK in full format.

/GROUP_SIZE

Output Save-Set Qualifier
Defines the number of blocks BACKUP places in each redundancy group.

Format

input-specifier output-save-set-spec/GROUP_SIZE=n

Description

BACKUP writes redundant information to output save sets to protect against data loss. Using the redundant information, BACKUP can correct one uncorrectable read error in each redundancy group.
The /GROUP_SIZE qualifier specifies the number of output blocks written to each redundancy group. The value of n can be 0 to 100. The default value is 10. If you define a value of 0 for /GROUP_SIZE, no redundancy groups are created for the save set.

Example


$ BACKUP/RECORD DBA1:[*...]/SINCE=BACKUP TAPE:SAVEWORK.BCK/GROUP_SIZE=5

This BACKUP command saves all files in the current default directory tree that have been modified since the last BACKUP/RECORD operation; the /GROUP_SIZE defines the redundancy group size as 5 blocks.

/HEADER_ONLY

Input File-Selection Qualifier
Specifies that only the file headers of a file are to be saved in a BACKUP operation.

Format

input-specifier /HEADER_ONLY=option output-specifier

Description

The /HEADER_ONLY qualifier specifies that the Backup utility is to save only the file header of a shelved or a preshelved file in a BACKUP operation.
When a file is shelved, the data in the file is shelved, but the file header is retained. Users shelve files to save disk space. (In addition, users might preshelve files to save time by performing shelving operations ahead of time.)
In a BACKUP save operation, the default behavior is to unshelve files before backing them up. This brings back the file data online, so that, when the BACKUP operation is performed, the entire file is backed up (not just the file header). The only exception to the BACKUP default behavior is in operations that use the /PHYSICAL or /IMAGE qualifier. For those operations, the file remains in the file shelved state.
For more information about file shelving and preshelving, see the Hierarchical Storage Management (HSM) documentation.
Use the following options with the /HEADER_ONLY qualifier:

Option Description

SHELVED Saves only the file header of a shelved file.

NOSHELVED Saves both the file header and the file data of a shelved file. (This causes the file to be unshelved.)

PRESHELVED Saves only the file header of a preshelved file.

NOPRESHELVE Saves both the file header and the file data of a preshelved file.

Examples

#1
$ BACKUP [INFO]/HEADER_ONLY=(SHELVED) MKA600:INFO.BCK/SAVE_SET

The command in this example saves all files in the directory [INFO] to a tape drive save set named INFO.BCK. The shelved files in [INFO] will not be unshelved. Only their file headers will be saved to save set INFO.BCK because the /HEADER_ONLY=(SHELVED) qualifier is specified.

#2
$ BACKUP [INFO]/HEADER_ONLY=(SHELVED,PRESHELVED) MKA600:INFO.BCK/SAVE_SET

This command saves all files in the directory [INFO] to a tape drive save set named INFO.BCK. The files saved from [INFO] will not be unshelved because the HEADER_ONLY=(SHELVED,PRESHELVED) qualifier is specified. The save set INFO.BCK will contain only the file headers of files that are shelved or preshelved.

#3
$ BACKUP/IMAGE DUA0: MKA600:INFO.BCK/SAVE_SET

The command in this example saves all files on the disk DKA0:. Because the /IMAGE qualifier is specified, only the file headers of files that are shelved or preshelved are saved to INFO.BCK.

#4
$ BACKUP [INFO] MKA600:INFO.BCK/SAVE_SET

The command in this example saves all files in the directory [INFO] to a tape drive save set named INFO.BCK. The files saved from [INFO] will be unshelved (the default). The save set INFO.BCK will contain both the file header and the data of files that are shelved or preshelved.

/IGNORE

Command Qualifier
Specifies that a BACKUP save or copy operation will override restrictions placed on files or will not perform tape label processing checks.

Note
File system interlocks are expressly designed to prevent data corruptions, and to allow applications to detect and report data access conflicts.
Use of the INTERLOCK keyword overrides these file data integrity interlocks. The data that BACKUP subsequently transfers can then contain corrupted data for open files. Also, all cases in which these data corruptions can occur in the data that BACKUP transfers are not reliably reported to you; in other words, silent data corruptions are possible within the transferred data.

Format

/IGNORE= option input-specifier output-specifier

Description

The /IGNORE= qualifier has the following options:
ACCESSIBILITY Processes files on a tape that is protected by a volume accessibility character, or on a tape created by HSC Backup. The option applies only to tapes. It affects the first tape mounted and all subsequent tapes in the save set.
INTERLOCK
Processes files that otherwise cannot be processed due to file access conflicts. Use this option to save or copy files currently open for writing. No synchronization is made with the process writing the file, so the file data that is copied might be inconsistent with the input file, depending on the circumstances (for example, if another user is editing the file, the contents might change). When a file open for writing is processed, BACKUP issues the following message:
%BACKUP-W-ACCONFLICT, 'filename' is open for write by another user.
The INTERLOCK option is especially useful if you have files that are open so much of the time that they might not otherwise be saved. The use of this option requires the user privilege SYSPRV, a system UIC, or ownership of the volume.
See the Note before this table for more information about this keyword.

LABEL_PROCESSING Saves or copies the contents of files to the specified magnetic tape volume regardless of the information contained in the volume header record. BACKUP does not verify the volume label or expiration date before writing information to the tape volume. Note that you cannot use this option with the /EXACT_ORDER qualifier.

LIMIT Prevents the target device from inheriting the volume expansion limit.

NOBACKUP Saves or copies both the file header record and the contents of files marked with the NOBACKUP flag by the /NOBACKUP qualifier of the DCL command SET FILE. If you do not specify this option, BACKUP saves only the file header record of files marked with the NOBACKUP flag.

Examples

#1
$ BACKUP/IGNORE=INTERLOCK _From: DUA0:[SUSAN...] _To: MTA0:SONGBIRD.BCK/LABEL=TAPE01

This command saves an entire directory tree and the files in all subdirectories, including any files that are open.

#2
$ BACKUP/IGNORE=LABEL_PROCESSING .;* MFA1:MYFILES.BCK/REWIND

This command rewinds the tape in drive MFA1 to the beginning-of-tape marker, initializes the tape, and creates a save set containing all files in the user's current directory. The command qualifier /IGNORE=LABEL_PROCESSING specifies that no tape label processing checks are done before BACKUP initializes the tape. When the tape is initialized, access to data that previously resided on the tape is lost.

#3
$ INITIALIZE/LABEL=VOLUME_ACCESSIBILITY:"K" MUA1: 29JUN $ BACKUP/IGNORE=(ACCESSIBILITY) _From: DUA0:[BOOKS...] _To: MUA1:BACKUP.SAV /LABEL=29JUN

The INITIALIZE command in this example initializes the tape with an accessibility character (K) and a volume label (29JUN). The BACKUP command mounts the tape, regardless of the accessibility, and performs the BACKUP operation. For more information about tape protection, see the HP OpenVMS System Manager's Manual.

$ BACKUP/LOG/IMAGE/CONVERT DKA500:[000000]IMAGE.BCK/SAVE DKA200:/NOINIT
%BACKUP-I-ODS5CONV, structure level 5 files will be converted to structure
        level 2 on DKA200:
-BACKUP-I-ODS5LOSS, conversion may result in loss of structure level 5
        file attributes
%BACKUP-S-CREATED, created DKA200:[000000]000000.DIR;1
%BACKUP-S-CREATED, created DKA200:[000000]BACKUP.SYS;1
%BACKUP-S-CREATED, created DKA200:[000000]CONTIN.SYS;1
%BACKUP-S-CREATED, created DKA200:[000000]CORIMG.SYS;1
%BACKUP-S-CREATED, created DKA200:[000000]SECURITY.SYS;1
%BACKUP-S-CREATED, created MDA2:[000000]TEST_FILES.DIR;1
%BACKUP-S-CREATEDAS, created DKA200:[TEST_FILES]SUB^_^{DIR^}.DIR;1 as
        DKA200:[TEST_FILES]SUB$$DIR$.DIR;1

You can use commands like the ones in the example if you have an image backup of an ODS-5 disk, and you want to restore it to an ODS-2 disk.
In the command line in the example, IMAGE.BCK is the ODS-5 save set, and DKA200: is the ODS-2 disk. When you use this conversion method, you must preinitialize the output disk to ODS-2 and then include the /NOINIT qualifier in your command line.

Contents

Index