HP OpenVMS System Management Utilities Reference
Manual
/IMAGE
Command Qualifier
Directs BACKUP to process an entire volume or volume set.
Beginning in Version 8.2, this qualifier has been supported for I64
system disks. The image of an I64 system disk can be saved and restored
on either an Alpha or an I64 system.
Format
/IMAGE input-specifier output-specifier
Description
To use the /IMAGE qualifier, you need write access to the volume index
file (INDEXF.SYS) and the bit map file (BITMAP.SYS), or the input
medium must be write-locked. BACKUP opens the index file to synchronize
with the file system (no update is made). Finally, you must have read
access to all files on the input medium.
You can receive a fatal error if you use /IMAGE with the qualifier.
When you use the /IMAGE qualifier to save to a disk, alias directory
trees are not processed.
Note
The input and output devices in an image operation must be different
except in an image save operation when the output device is a Files--11
disk save set.
|
If the output volume is a disk, all files on the output volume are
stored contiguously. Contiguous storage of files eliminates disk
fragmentation and creates contiguous free blocks of disk space.
Because all files on the input volume are processed, you cannot use
input file-selection qualifiers in image copy or save operations. You
can, however, restore files and directories selectively from an image
save set.
When performing image operations on volume sets (more than one volume),
the number of volumes specified by the output specifier must be equal
to the number of volumes in the input volume set.
In an image save or copy operation, BACKUP attempts to save or copy all
files on the input disk volume including files marked for deletion and
lost files (files without a directory entry). By default, a BACKUP
image operation saves or copies the attributes but not the contents of
files flagged as NOBACKUP.
Also by default, BACKUP does not save the attributes nor the contents
of files open for write access by another user at the time of the image
save operation. If you want these files to be included, specify the
command qualifier /IGNORE in the BACKUP command line. The command
qualifier /IGNORE=NOBACKUP directs BACKUP to save or copy files flagged
as NOBACKUP. The command qualifier /IGNORE=INTERLOCK directs BACKUP to
save or copy files open for write access by another user.
An image restore or copy operation initializes the output volume or
volume set. The initialization data comes from the save-volume summary
record of the input volume unless the command qualifier /NOINITIALIZE
is specified. Specifying /NOINITIALIZE directs BACKUP to initialize the
output volume using volume initialization data that already exists on
the output volume.
In image restore and copy operations, every file is restored or copied.
The output volume must be mounted using the /FOREIGN qualifier. The new
volume is a functionally equivalent copy of the input volume; however,
file placement will change. Files are stored contiguously on the output
volume.
You cannot change the structure level of the output volume in an image
restore or copy operation. A BACKUP operation to mixed tape and disk
save sets, as shown in the following command, is unsupported:
$ BACKUP SYS$DISK:/IMAGE dka0:FUN,MKA0:/SAVE/REW
|
Examples
| #1 |
$ MOUNT/FOREIGN DMA1:
%MOUNT-I-MOUNTED, mounted on NODE$DMA1:
$ BACKUP/IMAGE/LOG DLA2: DMA1:
%BACKUP-S-CREATED, created DMA1:[000000]000000.DIR;1
%BACKUP-S-CREATED, created DMA1:[000000]BACKUP.SYS;1
%BACKUP-S-CREATED, created DMA1:[000000]CONTIN.SYS;1
%BACKUP-S-CREATED, created DMA1:[000000]CORIMG.SYS;1
%BACKUP-S-CREATED, created DMA1:[000000]ELLA.DIR;1
%BACKUP-S-CREATED, created DMA1:[ELLA]SCAT.DAT;1
%BACKUP-S-CREATED, created DMA1:[000000]JOE.DIR;1
%BACKUP-S-CREATED, created DMA1:[JOE]STRINGS.DAT;1
%BACKUP-S-CREATED, created DMA1:[000000]OSCAR.DIR;1
%BACKUP-S-CREATED, created DMA1:[OSCAR]KEYS.DAT;1
%BACKUP-S-CREATED, created DMA1:[000000]VOLSET.SYS;1
.
.
.
$
|
The MOUNT command prepares the target disk for the image copy
operation. The command qualifier /LOG directs BACKUP to display
information about each file copied on your terminal. The BACKUP command
initializes DMA1 and copies the disk volume DLA2 to DMA1. All files on
DMA1 are stored contiguously.
| #2 |
$ BACKUP/IMAGE DBA2: MTA0:ET.BCK,MTA1:
|
This command saves an entire disk volume to a multivolume save set
named ET.BCK using two magnetic tape drives.
| #3 |
$ MOUNT/FOREIGN DBA1:
%MOUNT-I-MOUNTED, mounted on NODE$DBA1:
$ BACKUP/IMAGE WORKDISK DBA1:28SEP.BCK/SAVE_SET
|
The MOUNT command prepares the target disk for the image save
operation. The BACKUP command performs an image save operation to a
Files--11 save set named 28SEP.BCK.
/INCREMENTAL
Command Qualifier
Allows you to restore an incremental save set.
Note
/INCREMENTAL is valid only in restore operations. It is not related to
the /NOINCREMENTAL qualifier, which is valid only in BACKUP save
operations.
|
Format
/INCREMENTAL save-set-spec disk-device-name
Description
Use /INCREMENTAL only in restore operations that restore incremental
save sets. When you use /INCREMENTAL, the output specifier must specify
a device only; file specifications are not allowed. Also, input
save-set qualifiers are not allowed in incremental restore operations.
You can create incremental save sets with the command qualifier /RECORD
and the file-selection qualifier /SINCE=BACKUP or /SINCE=date. Most
sites perform daily incremental save operations to keep copies of files
created or modified that day, and periodic full backups to keep a copy
of all files on the disk volume. (HP recommends that you use the
command qualifier /IMAGE to perform full backups.)
If a disk volume is lost, corrupted, or destroyed, its contents can be
recreated by performing the following tasks:
- Restore the volume using the latest (most recent) image backup save
set. (The saveset must have been created using the /IMAGE and /RECORD
BACKUP command qualifiers.)
- Restore any incremental save sets since the last full backup, in
reverse chronological order, using the /INCREMENTAL qualifier.
After you restore the save sets in this order, the output disk volume
contains the same files it contained when the most recent incremental
save operation was performed.
When the /INCREMENTAL qualifier is used, the /BY_OWNER=ORIGINAL
qualifier is assumed; therefore, specifying /BY_OWNER is unnecessary
unless you want to change the original UICs. The /INCREMENTAL qualifier
can be used only on Files--11 Structure Level 2 or 5 volumes.
You can receive a fatal error if you use the /PHYSICAL qualifier with
/INCREMENTAL.
Example
If you have been performing a combination of full backups and
incremental save operations on a public volume, and the public volume
is lost, corrupted, or destroyed, use a procedure like the following
one to create a new copy of the public volume. First, restore the
volume from the latest full backup with an image restore operation.
The section "Formulating a Backup Strategy" in the BACKUP
chapter of the HP OpenVMS System Manager's Manual discusses the importance of using the
/IMAGE and /RECORD qualifiers the first time you back up a disk, before
you perform incremental backups.
$ MOUNT/FOREIGN DRA0:
%MOUNT-I-MOUNTED, mounted on _DRA0:
$ BACKUP/IMAGE/RECORD MTA0:FULLJUN02,MTA1 DRA0:
%BACKUP-I-RESUME, resuming operation on volume 2
%BACKUP-I-RESUME, resuming operation on volume 3
%BACKUP-I-RESUME, resuming operation on volume 4
.
.
.
$ DISMOUNT/NOUNLOAD DRA0:
|
Next, mount the disk as a file-structured volume and restore the
incremental save sets in reverse chronological order. Finally, restore
the weekly incremental save sets. The /INCREMENTAL qualifier must be
used where shown in the following example to obtain the correct results:
$ MOUNT DRA0: PUBLIC
%MOUNT-I-MOUNTED, PUBLIC mounted on _DRA0:
$ BACKUP/INCREMENTAL MTA0:INCD17JUN DRA0:
$ BACKUP/INCREMENTAL MTA0:INCD16JUN DRA0:
$ BACKUP/INCREMENTAL MTA0:INCD15JUN DRA0:
$ BACKUP/INCREMENTAL MTA0:INCW14JUN DRA0:
$ BACKUP/INCREMENTAL MTA0:INCW7JUN DRA0:
|
Note that BACKUP restores the volume correctly regardless of the order
in which the incremental save sets are applied; using reverse
chronological order is most efficient.
/INITIALIZE
Command Qualifier
Initializes an output disk or tape volume, making its entire previous
contents unavailable. (/REWIND performs the same function for output
tapes.)
Format
/[NO]INITIALIZE input-specifier output-specifier
Description
The /[NO]INITIALIZE qualifier is valid only when used with the command
qualifier /IMAGE during restore or copy operations or when saving files
to a sequential-disk save set.
When used with the command qualifier /IMAGE in a restore or copy
operation, the /INITIALIZE qualifier directs BACKUP to initialize the
output volume using volume initialization data from the save-volume
summary record on the input volume.
The /NOINITIALIZE qualifier directs BACKUP to reinitialize the output
volume using the existing initialization data on that volume; the
output volume must have been previously initialized as a Files--11
volume. When the output volume is initialized, existing data on the
volume is lost. The structure level of the output volume must be the
same as the structure level of the save set being restored.
Note
The BACKUP/NOINITIALIZE command does not preserve the dynamic volume
expansion characteristics of the output device. The reason is that the
target device is mounted foreign, preventing OpenVMS from obtaining the
expansion size and the logical size. To overcome this restriction, use
the /LIMIT and /SIZE qualifiers.
|
For image restore and copy operations on Files--11 volumes, the default
is /INITIALIZE.
If you use the /INITIALIZE qualifier when creating sequential-disk save
sets, BACKUP initializes the first output volume in the sequential-disk
save set, as well as subsequent volumes. By default, BACKUP does not
initialize the first volume of a sequential-disk save set but does
initialize subsequent volumes of a multivolume sequential-disk save set.
The BACKUP/IMAGE/INITIALIZE command sizes the storage bitmap to
correspond to the entire physical volume. Beginning with OpenVMS
Version 7.2, the file system also correctly handles a volume whose
storage bitmap is smaller than required. The space on the volume
available for allocation is the space the bitmap describes; as a
result, if the bitmap is smaller than the volume requires, not all the
volume is available for file allocation. A SHOW DEVICE /FULL command
continues to display the actual physical volume size; however, the free
blocks displayed are the number of blocks actually available for
allocation.
Examples
| #1 |
$ BACKUP/IMAGE/NOINITIALIZE DBA0: DBA2:
|
This command causes the output volume DBA2 to be reinitialized using
the volume initialization data that exists on DBA2. The contents of
DBA0 are then copied to DBA2.
| #2 |
$ BACKUP/IMAGE/INITIALIZE DBA2:OLDFILES.BCK/SAVE_SET DBA6:
|
This command directs BACKUP to initialize the output volume DBA6 using
volume initialization parameters in the save-volume summary record on
DBA2. The image save set OLDFILES.BCK is then restored to DBA6.
/INPUT_FILES
Input Save-Set Qualifier
Directs BACKUP to treat the input-specifier as the file name of a list
of files. This file specifies the input files for a BACKUP operation.
Format
input-specifier /INPUT_FILES output-specifier/SAVE_SET
Description
The /INPUT_FILES qualifier allows you to specify a list of files to be
processed for input. The input-specifier is the name of a file that
contains one standard OpenVMS file specification per line.
Example
|
$ BACKUP FILE.DAT/INPUT_FILES MKA600:INFO.BCK/SAVE_SET
|
The command in this example backs up the files listed in the FILE.DAT
file to a tape drive save set named INFO.BCK. If the disk, directory,
or file extension is not specified, the defaults are copied from the
previous entry or from the default if this is the first entry. The
FILE.DAT file contains the following entries:
$1$DKA0:[INFO]*.COM
INFO.TEXT
[PAYROLL]*.DAT
|
/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. (You can also specify /NOCONVERT with the /INTERCHANGE
qualifier.)
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.
/IO_LOAD
Command Qualifier
Beginning in OpenVMS Version 8.3, BACKUP is optimized to work more
efficiently with new storage controllers. You can use the /IO_LOAD
qualifier to increase or decrease the number of simultaneous I/Os
issued by the BACKUP utility. The default is 8 I/Os.
If the /IO_LOAD qualifier is omitted from the command line, the default
number of outstanding I/Os is still 8.
Format
/IO_LOAD [=n]
The value for n is an integer between 1 and the process AST
limit. The default value is 8.
Example
|
$ BACKUP DKA100: DKA400: /IMAGE /IO_LOAD=8
|
In this example, the /IO_LOAD=8 qualifier maintains 8 threads of I/O
reading data from the source disk. (BACKUP does not exceed 8
outstanding I/Os.)
/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-2002
Listing of BACKUP journal
Journal file _DB1:[SYSMGR]:ARCH.BJL;1 ON 7-OCT-2002 00:45:43.01
Save set WKLY.BCK, created on 6-OCT-2002 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, 2002, 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-2002 00:40:56.36
Save set 3OCT.FUL created on 3-OCT-2002 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-2002 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)
|
|
