HP OpenVMS Systems Documentation
HP OpenVMS System Management Utilities Reference Manual
SHUTDOWN shuts down the system and awaits a manual reboot. To use the new system parameter values generated in the SETPARAMS phase, specify either SHUTDOWN or REBOOT as the end phase. You can define the logical name AGEN$SHUTDOWN_TIME (using the DCL command DEFINE) to specify the number of minutes before shutdown occurs.
SHUTDOWN requires the SETPRV privilege.
REBOOT automatically shuts down and reboots the system, thus installing the new parameter values. To install the new system parameter values generated in the SETPARAMS phase, specify either SHUTDOWN or REBOOT as the end phase. You can define the logical name AGEN$SHUTDOWN_TIME (using the DCL command DEFINE) to specify the number of minutes before shutdown occurs.
REBOOT requires the SETPRV privilege.
HELP displays help information about AUTOGEN to the screen. The HELP
phase is only valid as the start phase command line parameter. When you
specify HELP for the start phase, the end phase and execution mode
parameters are ignored.
Specify an execution mode when you invoke AUTOGEN to control how AUTOGEN uses feedback. Table 6-2 lists the execution-mode options.
6.6 Files Used by AUTOGEN
Table 6-3 lists the files AUTOGEN uses during each phase.
1All files except VMSIMAGES.DAT, which contains the installed image list, reside in the SYS$SYSTEM directory. VMSIMAGES.DAT resides in the SYS$MANAGER directory.
2From software installation kit
3Also includes collected hardware configuration information
6.7 AUTOGEN Usage Summary
The AUTOGEN command procedure runs automatically when your system is installed or upgraded to set appropriate values for system parameters and sizes for system page, swap, and dump files.
Table 6-2 describes each execution-mode option.
To invoke AUTOGEN, use the following syntax to enter a command at the DCL command prompt:
Some layered products have their own special backup procedures. For more information, see the layered product documentation.
Also, when a symbolic link is encountered during a backup operation, the symbolic link itself is copied. This is true for all backup types --- physical, image, and file. For more information, see the Compaq C Run-Time Library Reference Manual for OpenVMS Systems.
Using BACKUP eliminates disk fragmentation. Fragmentation can occur as you create and extend files on a disk. If the file system cannot store files in contiguous blocks, it stores them in noncontiguous pieces. Eventually, the disk can become severely fragmented and system performance suffers. To eliminate fragmentation, perform an image backup of the disk and restore the backup copy. When you restore the image backup, BACKUP places the files on the disk contiguously.
Besides backing up your own files, directories, and disks, remember to back up your OpenVMS system disk. Depending on the policy at your site, individuals may be responsible for backing up their system disks, or an operator or system manager may perform the backup (as would likely be the case in a large, clustered computer system).
If you have access to the OpenVMS Alpha or Integrity servers CD-ROM, you can use a menu system supplied on the CD-ROM to back up your system disk.
For more information about standalone BACKUP and the menu-driven procedure, see the HP OpenVMS System Manager's Manual.
Because an image copy or backup operation processes all files on the input volume, you cannot specify file-selection qualifiers for these operations. You can, however, restore files and directories selectively from an image save set.
Beginning in Version 8.2, a restore of a physical backup no longer requires the output disk to have the same geometry (tracks, cylinders). The restore operation works as long as the output has the same or larger capacity.
To perform BACKUP operations, enter the DCL command BACKUP in the following format:
BACKUP input-specifier output-specifier
BACKUP evaluates the input and output specifiers to determine which
type of operation to perform. BACKUP also uses the input specifier to
locate the input and directs output to the output specifier.
7.3 BACKUP Input and Output Specifiers
BACKUP can process several different types of input and output. Depending on the type of operation being executed, input and output specifiers can be standard OpenVMS file specifications, BACKUP save-set specifications, or device specifications. Device specifications can refer to disk or magnetic tape volumes.
You can specify any valid OpenVMS file specification as BACKUP input or output specifiers; however, BACKUP does not allow node names in BACKUP file specifications. You can use wildcard characters, and you can also list multiple file specifications as input to a single BACKUP operation.
A BACKUP save-set specification is the file specification of a BACKUP save set. When you use BACKUP to save files or volumes, BACKUP writes your files to a save set. You can specify the save set as input to other BACKUP operations. When specifying a save set, follow the rules for specifying a OpenVMS file. The OpenVMS User's Manual describes valid specifications for disk files; the HP OpenVMS System Manager's Manual explains the rules for specifying magnetic tape files. A save-set specification has no default file type, although you can use BCK or SAV.
The save-set name can be any valid OpenVMS file name and type. However, when you create a save set on magnetic tape, the save-set name has the following restrictions:
Device specifications used as BACKUP input or output specifiers follow the conventions for specifying devices outlined in the OpenVMS User's Manual.
By default, BACKUP treats an input or output specifier referring to a Files--11 disk as a file specification. Therefore, to identify a save set on a Files--11 volume, you must include the /SAVE_SET qualifier with the specifier (see /SAVE_SET). BACKUP treats input and output specifiers referring to magnetic tape as save sets.
You cannot specify a save set for both the input and output specifier of a BACKUP command. For this reason, you cannot perform a BACKUP operation from one magnetic tape to another.
Table 7-1 shows input and output specifiers for each type of BACKUP operation.
|Save||BACKUP file-spec save-set-spec|
|Save (image)||BACKUP/IMAGE device-spec save-set-spec|
|Save (physical to disk)||BACKUP/PHYSICAL device-spec device-spec|
|Restore||BACKUP save-set-spec file-spec|
|Restore (image)||BACKUP/IMAGE save-set-spec device-spec|
|Restore (physical from disk)||BACKUP/PHYSICAL save-set-spec device-spec|
|Restore (physical from tape)||BACKUP/PHYSICAL save-set-spec device-spec|
|Copy||BACKUP file-spec file-spec|
|Copy (image)||BACKUP/IMAGE device-spec device-spec|
|Copy (physical to tape)||BACKUP/PHYSICAL device-spec save-set-spec|
BACKUP/COMPARE file-spec file-spec
BACKUP/COMPARE save-set-spec file-spec
BACKUP/COMPARE/IMAGE save-set-spec device-spec
BACKUP/COMPARE/IMAGE device-spec device-spec
BACKUP/COMPARE/PHYSICAL device-spec device-spec
BACKUP/COMPARE/PHYSICAL save-set-spec device-spec
|Create Journal||BACKUP/JOURNAL[=file-spec] file-spec save-set-spec|
An element list is a list of arguments specified with a command or qualifier. The arguments, or elements, in the list are separated by commas. Element lists relating to input or output specifiers are allowed only in the following circumstances:
$ BACKUP _From: DUA0:[DATA]A.DAT,B.DAT,[PROGRAMS]TEST.EXE _To: MSA0:TEST.SAV/LABEL=DLY101
$ BACKUP _From: DUA0:[DATA]*.*,DUA0:[PROGRAMS]*.* _To: MSA0:TEST.SAV,MSA1:/LABEL=WKLY01
$ BACKUP/IMAGE _From: MSA0:TEST.SAV,MSA1: _To: DUA0:[DATA...],DUA1:
BACKUP allows you to use wildcard characters in file specifications to represent directories, file names, file types, and version numbers. Omitted file names, file types, or version numbers are assumed to be the asterisk wildcard character (*). For instance, if you omit the version number, BACKUP processes all versions. (For introductory information about wildcard characters, see the OpenVMS User's Manual.)
You can use any valid DCL wildcard character with input specifiers that are Files--11 media or with the /SELECT and /EXCLUDE qualifiers. Note, however, that the symbols denoting the latest versions of files (;) and relative versions of files (;-n) are processed as the asterisk wildcard character (;*) when they are used with the /EXCLUDE and /SELECT qualifiers.
You cannot use wildcard characters in BACKUP save-set specifications unless the save sets are input specifiers on tape.
|omitted||If a directory name is omitted, BACKUP restores file to the current default directory .|
|[*...]||BACKUP restores files to the directory from which they were saved.|
|[directory]||BACKUP restores files to the named directory.|
|[directory...]||The wildcard characters used in the specification of the input files determine the directory to which BACKUP restores the files.|
If you specify directory wildcard characters incorrectly and your directories contain many levels of subdirectories, you risk losing the lower level subdirectories in BACKUP operations because OpenVMS directory trees can have only 8 levels with ODS-2 files. ODS-5 files, however, do not have this 8-level restriction.
$ BACKUP [OSCAR...] [JOE.RECEIVED...]
In this example, BACKUP creates a directory named [JOE.RECEIVED] (if it does not already exist) as well as subdirectories that correspond to the subdirectories of [OSCAR]. BACKUP copies all files from the directory [OSCAR] and its subdirectories to [JOE.RECEIVED] and its subdirectories. If [OSCAR] has 8 levels of directories, however, and files in it are ODS-2, BACKUP is unable to create a corresponding 9-level subdirectory to [JOE.RECEIVED]; the 8-level subdirectory to [OSCAR] is not copied. (This restriction does not apply to ODS-5 files.)
If you use the asterisk wildcard character (*) to represent subdirectories in the input specifier of a copy operation, BACKUP creates subdirectories to the directory specified in the output specifier that correspond to the subdirectories in the input specifier. BACKUP then copies all files from the lowest level subdirectory in the input specifier to the lowest level subdirectory in the output specifier. In the following example, the asterisk represents subdirectories named MONDAY and TUESDAY:
$ BACKUP [SAM.WORK.*.WEDNESDAY] [JAMES...]
In this example, BACKUP creates a subdirectory named [JAMES.MONDAY.TUESDAY.WEDNESDAY]. In doing so, BACKUP:
In a restore operation, the input specifier defaults to [*...] if the input save-set qualifier /SELECT is not used; this is important if you use the form [directory...] in the output specifier. The function of the wildcard [*...] is to carry over the entire directory name from the first level on and to place it before the ellipsis in the output specifier. Thus, if the save set in the following example contains the directory tree [SAVE...], the restored directory tree will be [WORK.SAVE...]:
$ BACKUP MTA0:SAVE.BCK [WORK...]
Note that the result will be the same, even if your output specifier has the same name as the directory in the input specifier, as shown in the following example:
$ BACKUP MTA0:SAVE.BCK [SAVE...]
The preceding command restores the directory tree [SAVE...] to a directory tree named [SAVE.SAVE...].
The following command restores the directory tree [SAVE...] to a directory tree named [WORK...]:
$ BACKUP MTA0:SAVE.BCK/SELECT=[SAVE...] [WORK...]
There are two ways to retain the original directory name when you restore files. You must either use the form [*...] for the output specifier, or you must specify the input save-set qualifier /SELECT. The following example uses the form [*...] in the output specifier to restore the directory tree [SAVE...] in save set SAVE.BCK to the directory tree [SAVE...]:
$ BACKUP MTA0:SAVE.BCK [*...]
The input save-set qualifier /SELECT causes only the ellipsis portion of the selected file specification to be carried over to the directory tree named in the output specifier [directory...]. The following command restores [SAVE...] to [SAVE...]: