Document revision date: 30 March 2001

## OpenVMS System Management Utilities Reference Manual

Previous | Contents | Index

## /INTERCHANGE

> Command Qualifier

> Directs BACKUP to process files in a manner suitable for data interchange (software distribution) by excluding information that would prevent other utilities or sites from reading the BACKUP save set.

> The /INTERCHANGE qualifier implies /CONVERT when the input is an ODS-5 disk or file.

### Format

> /INTERCHANGE input-specifier output-specifier

### Description

> The effects of the /INTERCHANGE qualifier are as follows:
> - Directories not selected as files are not copied.
> - Access control lists are not copied.
> - Block size on magnetic tape is limited to 8192 bytes.
> - Normal error recovery is used to write magnetic tapes so that no bad records exist on the resulting magnetic tape.

### Example

    $ BACKUP/RECORD/INTERCHANGE [ACCOUNTS]/SINCE=BACKUP MFA0:SAVACC.BCK

> The command in this example saves all files in the directory [ACCOUNTS] that have been modified since the last BACKUP/RECORD operation. The /INTERCHANGE qualifier ensures that the processed files are suitable for data interchange.

## /JOURNAL

> Command Qualifier

> Specifies that a BACKUP save operation is to create a BACKUP journal file or append information to a BACKUP journal file. Lists the contents of a BACKUP journal file when combined with the command qualifier /LIST.

### Format

> /JOURNAL [=file-spec] input-specifier output-specifier

> /JOURNAL [=file-spec]/LIST[=file-spec]

### Description

> A BACKUP journal file contains records of BACKUP save operations and the file specifications of saved files. Use the command qualifier /JOURNAL[=file-spec] in a BACKUP save operation to create a journal file.

> If you do not include a file specification with the command qualifier /JOURNAL, the name of the BACKUP journal file defaults to SYS$DISK:[]BACKUP.BJL. You can specify another file name, however. (The file specification of a journal file cannot include a node name; the default file type for a journal file is .BJL.) If the specified journal file does not exist, it is created; if the journal file does exist, the new journal information is appended to the existing journal file.

> Start a new version of a journal file by creating a zero-length file using the DCL command CREATE or a text editor.

> To list the contents of a BACKUP journal file, use the /JOURNAL=[file-spec] qualifier with the /LIST qualifier, but do not specify an input or output specifier. By default, the list is displayed on SYS$OUTPUT, but it is written to an output file if you specify a file with /LIST.

> When listing a journal file, you can use the file-selection qualifiers /BEFORE, /SINCE, and /EXCLUDE to search for specific files. (In this context, the /BEFORE and /SINCE qualifiers refer to the time when the save set was created, not the time when the files in the save set were created.) Also, by specifying a file in a multivolume save set, you can search the journal file to find which volume the file is in. You can then mount that volume and restore the file.

> Journal files are not created for physical save operations (save operations performed with the command qualifier /PHYSICAL). You can receive a fatal error if you use the /PHYSICAL qualifier with /JOURNAL.

###

#### Examples

#1
    $ BACKUP/JOURNAL=LAR.BJL [LARRY]*.*;* MFA0:YET.BCK

> This command saves all versions of all files in the directory [LARRY] to the save set YET.BCK on MFA0. The /JOURNAL qualifier creates a record of the saved files in a journal file named LAR.BJL in the current default directory.

#2
    $ BACKUP/LIST/JOURNAL=ARCH.BJL/SELECT=[SMITH.PROGS]/SINCE=5-OCT-2000
    Listing of BACKUP journal
    Journal file _DB1:[SYSMGR]:ARCH.BJL;1 ON 7-OCT-2000 00:45:43.01
    Save set WKLY.BCK, created on 6-OCT-2000 00:01:34.54
    Volume number 1, volume label WKL101

             [SMITH.PROGS]REMINDER.FOR;46
             [SMITH.PROGS]RUNTHIS.FOR;4
             [SMITH.PROGS]TIMER.PAS;5

    .
    .
    .

> This example displays all files in the directory [SMITH.PROGS] that were saved after October 5, 2000, and listed in the BACKUP journal file ARCH.BJL.

#3
    $ BACKUP/JOURNAL/LOG/IMAGE  DRA2: MTA0: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 _MTA0: 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]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

> This example shows how to create a BACKUP journal file and list the contents of the BACKUP journal file.

## /LABEL

> Output Save-Set Qualifier

> Specifies the volume labels for the magnetic tapes to which the save set is written.

### Format

> input-specifier output-save-set-spec/LABEL=(string[,...])

### Description

> Use the /LABEL Qualifier to specify the one- to six-character volume labels for the magnetic tapes to which the save set is written.

> You can specify either a single label or a list of labels with the /LABEL qualifier. If you do not specify the /LABEL qualifier, BACKUP uses the first six characters of the save-set name as the volume label of the first tape. If you specify a label that is longer than six characters, BACKUP truncates the label to six characters.

> If the save set continues to another tape, and you did not specify a volume label for the tape, BACKUP uses the first four characters of the previous tape's volume label followed by the volume number of the tape. For example, if the first tape in a save set is labeled AAAABB, the second tape in a save set is labeled AAAA02, and the third tape is labeled AAAA03.

> Before writing a save set to magnetic tape, BACKUP compares the label specified in the command line to the volume label of the tape. (If the tape has no volume label and you specified the output save-set qualifier /REWIND, BACKUP writes the label you specified to the volume header record of the tape.) If the volume label has fewer than six characters, BACKUP pads the volume label with the blank character to six characters.

> The first four characters of the volume label must either exactly match the first four characters of the label specified in the BACKUP command line, or the first four characters of the volume label 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 either the fifth or the sixth character of the volume label is in the range 0 to 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 match the corresponding characters in the label specified in the BACKUP command line exactly.

> The following table illustrates volume labels that match labels specified in the BACKUP command line:

> Label Specified in the Command Line | Matching Volume Labels
> --- | ---
> MAR | MAR, MAR_, MAR_nn
> MAR_ | MAR_, MAR_nn
> MARK | MARK, MARKnn
> MARKER | MARKER, MARKnn

> If the label you specify matches the tape's volume label, the BACKUP save operation proceeds. If you specify more than one label with the /LABEL qualifier, the BACKUP save 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 save operation will succeed if you specify the following list of labels with the /LABEL qualifier:

>     /LABEL=(MA1684,MA1685,MA1686)

> If the label you specified does not match the tape's volume label, BACKUP displays the following messages and prompt on your terminal if you specified the command qualifier /NOASSIST, or on the operator terminal if you did not specify /NOASSIST:

>     %BACKUP-W-MOUNTERR, volume 'number' on 'device' was not mounted because
>     its label does not match the one requested
>     Specify option (QUIT, NEW tape or OVERWRITE tape)
>     BACKUP>

> Specify QUIT to abort the BACKUP operation and unload the magnetic tape. Specify NEW to direct BACKUP to prompt for a new tape. Specify OVERWRITE to direct BACKUP to ignore the label mismatch, mount the tape, initialize the tape if you specified the output save-set qualifier /REWIND, and write the save set to the tape.

> You can specify the command qualifier /IGNORE=LABEL_PROCESSING to prevent BACKUP from verifying the volume label of the tape. You can also use the /EXACT_ORDER qualifier to specify the exact order of tape volume labels that you want to use in a BACKUP operation.

###

#### Examples

#1
    $ BACKUP [PAYROLL] MTA0:30NOV.BCK/LABEL=PAY

> This command causes BACKUP to check the volume label of the tape mounted on drive MTA0. If the volume label is PAY, BACKUP saves the directory [PAYROLL] to a save set named 30NOV.BCK.

#2
    $ BACKUP DDA1: MTA0:PLAYS.BCK,MTA1,MTA2/REWIND/LABEL=(ACT1,ACT2,ACT3)

> This example assumes that the three tapes have no volume labels. This command saves all files on the disk named DDA1 to the save set PLAYS.BCK. The first tape in the save set is labeled ACT1, the second is labeled ACT2, and the third is labeled ACT3.

## /LIST

> Command Qualifier

> Lists information about a BACKUP save set and about the files in a save set. You can display the list on your terminal or write it to a file.

### Format

> /LIST [=file-spec] save-set-spec

### Description

> Use the /LIST qualifier by itself or in conjunction with any other operation (save, restore, copy, compare, or journal). If /LIST is specified by itself (not with a save, restore, copy, compare or journal operation), the input specifier must refer to a save set, and the output specifier must be omitted.

> Before you can list the contents of a save set, the media containing the save set must be inserted into an appropriate drive. If the save set is stored on a disk, the disk must be mounted as a Files--11 volume or as a foreign volume. BACKUP mounts magnetic tapes automatically as part of the list operation.

> By default, the list information is displayed on your terminal; however, you can specify a file to which the list information can be written.

> When you use the /LIST qualifier with standalone BACKUP and you direct output to a file (/LIST=file-spec), the file specification must refer to either a terminal or a printer.

> You can use either the command qualifier /BRIEF or /FULL with the /LIST qualifier. The /BRIEF qualifier directs BACKUP to list each file's size in blocks and its creation date. The /FULL qualifier directs BACKUP to list additional information about each file in the same format as the information provided by the DCL command DIRECTORY/FULL. The default is /BRIEF.

> Do not use the command qualifier /LOG with /LIST when the output for /LIST is directed to the terminal; if you do, you will receive confusing output.

### Example

    $ BACKUP/LIST DBA2:[SAVE]23MAR00.BCK/SAVE_SET

    Listing of save set(s)

    Save set:          23MAR00.BCK
    Written by:        MOROCI
    UIC:               [000200,000200]
    Date:              23-MAR-2000 14:18:16.00
    Command:           BACKUP [SAVE] DBA2:[SAVE]23MAR00.BCK/SAVE_SET

    Operating system:  OpenVMS Alpha Version V7.3

    BACKUP version:    V7.3
    CPU ID register:   08000000
    Node name:         _SUZI::
    Written on:        _DBA2:
    Block size:        32,256
    Group size:        10
    Buffer count:      3

    [SAVE]LAST.DAT;1                         1  18-JAN-2000 14:11
    [SAVE]INFO.TXT;4                         5   4-FEB-2000 13:12
    [SAVE]WORK.DAT;3                        33   1-JAN-2000 10:02

    Total of 3 files, 39 blocks
    End of save set

> This command lists the BACKUP summary information and the file name, size, and creation date for each file in the save set. Note that the /SAVE_SET qualifier is required to identify the input specifier as a save set on a Files--11 disk.

## /LOG

> Command Qualifier

> Determines whether the file specification of each file processed is displayed on SYS$OUTPUT during the operation. The default is /NOLOG.

### Format

> /[NO]LOG input-specifier output-specifier

### Example

    $ BACKUP/LOG [SAVE]23MAR00.BCK/SAVE_SET DBA2:[PLI.WORK]
    %BACKUP-S-CREATED, created DBA2:[PLI.WORK]ANOTHER.DAT;1
    %BACKUP-S-CREATED, created DBA2:[PLI.WORK]LAST.DAT;1
    %BACKUP-S-CREATED, created DBA2:[PLI.WORK]THAT.DAT;1
    %BACKUP-S-CREATED, created DBA2:[PLI.WORK]THIS.DAT;2
    .
    .
    .

> In this example, the file specifications of the files restored to the directory named [PLI.WORK] on DBA2 are logged to SYS$OUTPUT.

## /MEDIA_FORMAT=[NO]COMPACTION

> Output Save-Set Qualifier

> Controls whether data records are automatically compacted and blocked together. Data compaction and record blocking increase the amount of data that can be stored on a single tape cartridge.

> The compaction ratio depends on the data and the tape drive you use. For more information, refer to the documentation supplied with your tape drive.

> BACKUP allows you to specify different compaction settings on different save sets on a tape. However, not all tape drives support the use of more than one compaction setting on a tape. Whether mixed mode tapes are permitted depends on the model of the tape drive you use.

### Format

> input-specifier output-save-set-spec /MEDIA_FORMAT=[NO]COMPACTION

### Description

> The /MEDIA_FORMAT qualifier can only be used with tape drives that support data compaction.

> On Alpha systems, you can use the /MEDIA_FORMAT=COMPACTION qualifier for hardware data compaction of SCSI tape drives.

### Example

    $ BACKUP WORK$:[TESTFILES...]*.*;*  MUA0:TEST.SAV -
    _$/MEDIA_FORMAT=COMPACTION /REWIND

> This command saves all files in the directory [TESTFILES] and its subdirectories in 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.

## /MODIFIED

> Input File-Selection Qualifier

> Selects files according to the value of the modified date field (the date the file was last modified) in each file header record.

### Format

> input-specifier/BEFORE=time /MODIFIED output-specifier

> input-specifier /SINCE=time /MODIFIED output-specifier

### Description

> You must use the /MODIFIED qualifier with either of the input file-selection qualifiers /BEFORE or /SINCE. The date and time you specify with /BEFORE or /SINCE determines which files are processed.

> You cannot use /MODIFIED with the input file-selection qualifiers /BACKUP, /CREATED, or /EXPIRED.

### Example

    $ BACKUP [SUNDANCE...]/BEFORE=TODAY/MODIFIED MFA1:MOD.BCK

> This command saves all files in the directory tree [SUNDANCE] whose modification dates precede today (00:00:00.0 o'clock of the current day, month, and year).

## /NEW_VERSION

> Output File Qualifier

> Creates a new version of a file if a file with an identical specification already exists at the location to which the file is being restored or copied.

### Format

> input-specifier output-specifier/NEW_VERSION

### Description

> If BACKUP attempts to copy or restore a file when a file with an identical directory name, file name, type, and equal or higher version number already exists, a new file is created with the same name and type and a version number one higher than the highest existing version.

> If you do not use /NEW_VERSION, /REPLACE, or /OVERLAY, and the version number of the file being restored is equal to or less than the version number of the existing file, BACKUP reports an error in copying or restoring the file.

> Note that when copying or restoring files using the /NEW_VERSION qualifier, files are processed in decreasing version number order and are created in ascending order. The result is that the version numbers are inverted.

> Because this qualifier causes version numbers to change, using it with the /VERIFY qualifier will cause unpredictable results. Compaq recommends that you do not use the /NEW_VERSION qualifier with the /VERIFY qualifier.

### Example

    $ BACKUP MTA1:NOV30REC.BCK/SELECT=*.DAT [RECORDS...]/NEW_VERSION

> This example restores all files with the file type of .DAT from the magnetic tape save set NOV30REC.BCK to the directory [RECORDS]. The /NEW_VERSION qualifier instructs BACKUP to restore each file with the file type .DAT regardless of whether a file with the same file specification already exists.

## /NOINCREMENTAL

> Command Qualifier

> Beginning with OpenVMS Version 7.2, on a save operation /NOINCREMENTAL allows you to control the amount of file data that is saved. Use this qualifier only if you are sure that you want to save specific files and do not want to save all data.

### Format

> /NOINCREMENTAL input-specifier output-specifier

### Description

> In OpenVMS Version 6.2 and prior versions, the system, by default, did not save files and subdirectories that were under directories that had been modified. In OpenVMS Versions 7.0 and 7.1, to ensure a successful restore, the system saved all files and subdirectories under directories that had been modified. This behavior, however, sometimes resulted in saving files and subdirectories that were not needed for later restore operations.

> /NOINCREMENTAL has no meaning in a restore operation.

### Example

    $ BACKUP/ FAST/ NOINCREMENTAL /SINCE="3-MAY-2000" -
    _$ MAC_DISK:[000000...]*.*;* -
    _$ TAPE:MCDSK000503.BCK/ SAVE/ REWIND

> The command in this example executes an incremental save BACKUP operation for an input volume; the command avoids saving all files under recently modified directories.

## /OVERLAY

> Output File Qualifier

> Writes the input file over a file with an identical specification at the output location.

### Format

> input-specifier output-specifier/OVERLAY

### Description

> If BACKUP attempts to copy or restore a file when a file with an identical directory name, file name, type, and version number already exists, the new version of the file is written over the existing version. The file identification of the new version is the same as the file identification of the file that is overwritten.

> The physical location of the file on disk does not change. If /OVERLAY is specified, and the new file is larger than the one already present, BACKUP allocates more blocks on the disk and extends the file.

> When you do not use /OVERLAY, /REPLACE, or /NEW_VERSION, and the version number of the file being restored is identical to the version number of the existing file, BACKUP reports an error in copying or restoring the file.

### Example

    $ BACKUP DRA1:MAR30SAV.BCK/SAVE_SET [RECORDS...]/OVERLAY

> The sequential-disk save set MAR30SAV.BCK is restored to the directory tree [RECORDS...]. If a file from the save set has a specification that is identical to a file that already exists in [RECORDS...], the /OVERLAY qualifier directs BACKUP to write over the existing version.

Previous | Next | Contents | Index

| privacy and legal statement |
6048PRO_019.HTML