Updated: 11 December 1998 |
OpenVMS System Manager's Manual
Previous | Contents | Index |
Because of the way volume shadowing duplicates data on each disk in the shadow set, there are special considerations for restoring a shadow set. To restore a shadow set, refer to Volume Shadowing for OpenVMS.
Because the BACKUP output device (the shadow set) must be mounted using the /FOREIGN qualifier, Compaq does not support a restore operation from an image save set to a virtual unit. |
Backing up your system disk is critical for the following reasons:
If you have access to the OpenVMS Alpha or VAX operating system distribution compact disc, back up your system using the menu system provided on the disc. For more information about using the menu system, see Section 10.17.1.
If you use the menu system to back up large system disks on low memory VAX systems (those with less than 32 MB of memory), BACKUP might need to page and thereby cause the operation to fail. If this problem occurs, use standalone BACKUP to back up system disks on VAX systems. |
If you do not have access to the OpenVMS VAX operating system
distribution compact disc, use standalone BACKUP to back up and restore
your system disk. For more information about standalone BACKUP, see
Section 10.17.2.
10.17.1 Starting the Menu System
Use the menu system in this section to back up or restore system disks and user disks if you have access to the OpenVMS Alpha or VAX Version operating system distribution compact disc.
$ @SYS$SYSTEM:SHUTDOWN |
SYSTEM SHUTDOWN COMPLETE |
USE CONSOLE TO HALT SYSTEM |
The boot command you use for your computer depends on the type of system you have. For more information about booting your system, see the installation and operations supplement for your computer. |
The following example shows how to start the menu system on an OpenVMS VAX system:
>>> B/R5:10000100 ESA0 Bootfile: ISL_SVAX_071 -ESA0 Network Initial System Load Function Version 1.1 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3 OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2 Enter a Known Service Name: VMS071 OpenVMS VAX Version 7.2 Major version id = 1 Minor version id = 0 %SYSINIT-E, error opening page file, status = 0000025C %SYSINIT-E, error opening swap file, status = 0000025C %SYSINIT, primary PAGEFILE.SYS not found; system initialization continuing %SYSINIT, no dump file - error log buffers not saved %SYSINIT-E, error mounting system device, status = 00000F64 $! Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. $set noverify Copyright © (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... **************************************************************** The menu can be used to execute DCL commands and procedures for various "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1 Execute DCL commands and procedures 2) Shut down this system Enter CHOICE or "?" to repeat menu: (1/2/?)) 1 WARNING -- The normal VMS startup procedure has not executed. Some commands and utilities will not work as documented. Enter DCL commands -- Enter "LOGOUT" when done. When you enter "LOGOUT" a logout message will be displayed, and you will be returned to the menu. $$$ |
The Backup utility (BACKUP) does not copy open files (for example, accounting files or operator log files). For this reason you should use standalone BACKUP (VAX only) or the menu system (if your configuration permits) to back up your system disk. You can boot standalone BACKUP into the main memory of your computer (while the operating system is shut down) and use a subset of BACKUP command qualifiers to perform a complete backup of every file on the system disk. Standalone BACKUP is supported only for OpenVMS VAX installations and for backing up and restoring your system disk. Table 10-8 lists the qualifiers that you can use with standalone BACKUP.
Type | Qualifier | Default |
---|---|---|
Command Qualifiers | /BRIEF | /BRIEF |
/COMPARE | None | |
/FULL | /BRIEF | |
/IMAGE | /IMAGE | |
/[NO]INITIALIZE | Refer to the OpenVMS System Management Utilities Reference Manual | |
/LIST[=file-spec] | Refer to the OpenVMS System Management Utilities Reference Manual | |
/[NO]LOG | /NOLOG | |
/PHYSICAL | None | |
/RECORD | None | |
/[NO]TRUNCATE | /NOTRUNCATE | |
/VERIFY | None | |
/VOLUME=n | None | |
Input Save-Set Qualifiers | /[NO]CRC | /CRC |
/[NO]REWIND | /NOREWIND | |
/SAVE_SET | None | |
Output Save-Set Qualifiers | /BLOCK_SIZE=n | Refer to the OpenVMS System Management Utilities Reference Manual |
/BY_OWNER=uic | Refer to the OpenVMS System Management Utilities Reference Manual | |
/COMMENT=string | None | |
/[NO]CRC | /CRC | |
/DENSITY=n | Refer to the OpenVMS System Management Utilities Reference Manual | |
/[NO]EXACT_ORDER | /NOEXACT_ORDER | |
/GROUP_SIZE=n | /GROUP_SIZE=10 | |
/LABEL=(string[,...]) | Refer to the OpenVMS System Management Utilities Reference Manual | |
/PROTECTION[=(code)] | Refer to the OpenVMS System Management Utilities Reference Manual | |
/[NO]REWIND | /NOREWIND | |
/SAVE_SET | None | |
/TAPE_EXPIRATION | Today |
You should have a standalone BACKUP kit that came with your OpenVMS distribution kit; however, depending on the type of media you have, standalone BACKUP boots faster if you build it on the system disk or a user disk. The installation and upgrade supplement for your computer contains instructions for building and booting standalone BACKUP on several types of media.
This section provides information about building standalone BACKUP on a
disk or tape and using it to back up your system disk.
10.17.2.1 Building Standalone BACKUP on a Disk (VAX Only)
Standalone BACKUP boots faster on disk than it does on tape. For this reason, you should create a standalone BACKUP kit on disk.
You can build standalone BACKUP on either the system disk or a user disk. If you build standalone BACKUP on a user disk, the kit occupies more disk space than if you build it on the system disk. This is because certain files that boot the system already exist on the system disk.
To build standalone BACKUP, execute SYS$UPDATE:STABACKIT.COM. The procedure copies the files for booting standalone BACKUP to a new directory on the target device that you specify, creating the directory if necessary. When you build a kit on the system disk, the procedure copies the files to the [SYSE] directory. When you build the kit on a user disk, the procedure copies the files to the [SYS0] directory.
Perform the following steps to build standalone BACKUP on a disk:
$ @SYS$UPDATE:STABACKIT Enter the name of the device on which to build the kit: |
Enter the name of the device on which to build the kit: SYS$SYSDEVICE: |
The kit is complete. |
Performing Image Backups from an RF73 Disk
When you perform an image backup from an RF73 disk (or a disk with a cluster size of 4 blocks) to an RF74 disk (or a disk with a cluster size of 7 blocks), the Backup utility does not check the file size when it allocates space for the file being copied. Therefore, if the file has an allocation greater than the value of the CLUSTER_SIZE attribute established during initialization, BACKUP allocates one more cluster size number of blocks to the allocation size even though the actual file size is less than the cluster size. For example, during an image backup, a file that uses 6 blocks and is allocated 8 blocks (which displays as 6/8 on the screen if you enter a DIRECTORY/SIZE=ALfter it is copied to the target disk.
As a result of this problem, the following files are copied to the image system disk with a blocks used/allocation size of 6/14 blocks:
This incorrect allocation size causes standalone BACKUP to fail on the booted image system disk.
To correct this problem, recopy the two previously listed files to the same directory after the image backup, by using the following command (which also specifies the correct allocation size):
$ COPY/ALLOCATION=7 SYS$COMMON:[SYS$LDR]LIDRIVER.EXE $ COPY/ALLOCATION=7 SYS$COMMON:[SYS$LDR]LPDRIVER.EXE |
To boot standalone BACKUP from a disk, perform the following steps:
$ @SYS$SYSTEM:SHUTDOWN |
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM |
>>> B/n0000000 device-name |
>>> B/E0000000 DKA400 |
OpenVMS VAX Version Vn.n Major version id = 01 Minor version id = 00 |
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-JAN-1998 15:00 |
Available device MKA500: device type TK50 Available device DKA100: device type RRD40 . . . |
%BACKUP-I-IDENT, Standalone BACKUP Vn.n; the date is 19-APR-1998 15:00 $ |
On VAX systems with a tape cartridge distribution kit, the tape cartridge that came with your distribution kit contains standalone BACKUP. Use the procedure in this section if your copy of standalone BACKUP becomes damaged or if you want to make extra copies.
To build standalone BACKUP on a tape cartridge, perform the following steps:
$ @SYS$UPDATE:STABACKIT |
Enter the name of the device on which to build the kit: MUA0 |
Please place the scratch tape cartridge in drive _MUA0: This volume will receive the volume label SYSTEM. Enter "YES" when ready: |
Ending time 19-MAY-1998 16:44:29.90 Starting time 19-MAY-1998 16:30:39.05 The Kit is complete. $ |
If the disk containing standalone BACKUP becomes unusable (for example, if the drive fails), you can boot standalone BACKUP from a tape cartridge. Booting standalone BACKUP from a tape cartridge takes approximately 20 minutes.
To boot standalone BACKUP from a tape cartridge, use the following procedure:
$ @SYS$SYSTEM:SHUTDOWN |
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM |
>>> BOOT MUA0 |
OpenVMS VAX Version V7.2 Major version id = 1 Minor version id = 0 |
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-MAY-1998 15:00 |
Available device DUA0: device type Generic_DU Available device MUA0: device type TK50 |
%BACKUP-I-IDENT, standalone BACKUP V7.2; the date is 19-MAY-1998 15:50 $ |
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6017PRO_049.HTML
|