Document revision date: 19 July 1999

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.

Backing up your system disk is critical for the following reasons:

• A system disk could become inoperable if a problem occurs during a software upgrade, update, or installation. Before you attempt any of these operations, back up the system disk. If a problem occurs, you can restore the backup copy of the system disk.
• System files could inadvertently be deleted. After you install, upgrade, or update the operating system or any other software products, back up the system disk. If a system file is deleted, you can restore the backup copy and continue to use the system.
• The drive that holds the system disk could malfunction. If you have a backup copy of the operating system and your other software, you can restore it to a functioning disk and continue to use the system.
• Disk fragmentation could occur if files are stored noncontiguously on the disk. Perform an image backup of the system disk to a magnetic tape or another disk and then restore the files to the original system disk. This restores the system disk and contiguously stores files. You can also eliminate fragmentation by performing a disk-to-disk image backup without using the /SAVE_SET qualifier. This creates a functionally equivalent copy of the entire system disk, on which files are stored contiguously. (See Section 10.17.5.)

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 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.

How to Perform This Task

1. If the operating system is not running, go to step 2.
   If the operating system is running, log in to the SYSTEM account. Enter the following command and press Return:

   $ @SYS$SYSTEM:SHUTDOWN

   
   Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE

   
   On VAX systems, the following message is also displayed:

   USE CONSOLE TO HALT SYSTEM

   
   Halt the system if you see this message.

2. Boot the system:
   • On OpenVMS Alpha systems, boot the distribution compact disc.
   • On OpenVMS VAX systems, boot the distribution compact disc from the SYS1 directory.

   Note 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.

3. When the system boots, it displays a menu. Choose the menu item that allows you to execute DCL commands and procedures.
4. At the DCL prompt, you can back up or restore the system and user disks.
   To make a backup copy of the system disk, see Section 10.17.3.
   To restore the system disk, see Section 10.17.4.

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

10.17.2 Understanding Standalone BACKUP (VAX Only)

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.

Table 10-8 Valid Standalone BACKUP Qualifiers

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.

How to Perform This Task

Perform the following steps to build standalone BACKUP on a disk:

1. Log in to the SYSTEM account.
2. Enter the following command and press Return:

   $ @SYS$UPDATE:STABACKIT Enter the name of the device on which to build the kit:

3. Enter the device name of the disk that you are building standalone BACKUP on. If you are building standalone BACKUP on the system disk, enter SYS$SYSDEVICE. For example:

   Enter the name of the device on which to build the kit: SYS$SYSDEVICE:

4. The procedure places the files in the appropriate directories on the disk that you are using to build standalone BACKUP. It lists the files as they are copied. When the procedure finishes, it displays the following message:

   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:

• SYS$COMMON:[SYS$LDR]LIDRIVER.EXE
• SYS$COMMON:[SYS$LDR]LPDRIVER.EXE

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

10.17.2.2 Booting Standalone BACKUP from a Disk (VAX Only)

To boot standalone BACKUP from a disk, perform the following steps:

1. If the operating system is not running, go to step 2.
   If the operating system is running, log in to the SYSTEM account. Enter the following command and press Return:

   $ @SYS$SYSTEM:SHUTDOWN

   
   Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM

2. Halt the system.
3. Boot standalone BACKUP from the root where the kit is located. The exact commands for booting standalone BACKUP differ among the various computer models. Refer to the upgrade and installation supplement for your computer for booting information.
   For example, to boot a MicroVAX 3100 computer, use the following format:

   >>> B/n0000000 device-name

   
   where:

   • n is the number of the root on the disk containing the standalone backup.
   • device-name is the device name of the disk.
   
   For example, if the disk has a device name of DKA400:, and the standalone BACKUP kit was created in the [SYSE] directory, enter the following command:

   >>> B/E0000000 DKA400

   
   For more information about device names, see Section 7.1.

4. Standalone BACKUP displays the following message:

   OpenVMS VAX Version Vn.n Major version id = 01 Minor version id = 00

5. The procedure asks you for the date and time. Enter the date and time using the 24-hour clock format and press Return. For example:

   PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-JAN-1998 15:00

6. The procedure displays a list of the local devices on your system. For example:

   Available device MKA500: device type TK50 Available device DKA100: device type RRD40 . . .

   
   Check the list of devices. If the list is incomplete, make sure that all the drives are properly connected to the system. Refer to your hardware manuals for details.

7. When standalone BACKUP finishes booting, it displays an identification message followed by the dollar sign prompt ($):

   %BACKUP-I-IDENT, Standalone BACKUP Vn.n; the date is 19-APR-1998 15:00 $

   
   To make a backup copy of the system disk, see Section 10.17.3.
   To restore the system disk, see Section 10.17.4.

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.

How to Perform This Task

To build standalone BACKUP on a tape cartridge, perform the following steps:

1. Obtain a blank, initialized tape cartridge. Write the name S/A BKUP V7.2 on the paper label. Insert the label into the label slot.
2. Write-enable the tape cartridge by sliding the write-protect switch away from the label slot.
3. Insert the tape cartridge labeled S/A BKUP V7.2 into the drive.
4. Log in to the SYSTEM account.
5. Enter the following command:

   $ @SYS$UPDATE:STABACKIT

6. The procedure asks you for the name of the target device. Enter the device name of the tape cartridge drive you are using to build standalone BACKUP. For example:

   Enter the name of the device on which to build the kit: MUA0

7. The procedure displays the following message:

   Please place the scratch tape cartridge in drive _MUA0: This volume will receive the volume label SYSTEM. Enter "YES" when ready:

8. When you are ready to continue, enter YES.
9. The system displays verification messages informing you that files are being copied.
10. When standalone BACKUP is built, the procedure displays a message similar to the following one:

    Ending time 19-MAY-1998 16:44:29.90 Starting time 19-MAY-1998 16:30:39.05 The Kit is complete. $

11. Remove the tape cartridge labeled S/A BKUP V7.2 from the tape cartridge drive.
12. Write-protect the tape cartridge by sliding the write-protect switch toward the label slot. Store the cartridge in a safe place.

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.

How to Perform This Task

To boot standalone BACKUP from a tape cartridge, use the following procedure:

1. If the operating system is not running, see step 2.
   If the operating system is running, log in to the SYSTEM account. Enter the following command and press Return:

   $ @SYS$SYSTEM:SHUTDOWN

   
   Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM

2. Halt the system.
3. Insert the tape cartridge that contains standalone BACKUP into the tape cartridge drive.
4. To boot standalone BACKUP, enter the BOOT command followed by the device name of the tape cartridge drive that contains standalone BACKUP. For example:

   >>> BOOT MUA0

5. Standalone BACKUP displays the following message:

   OpenVMS VAX Version V7.2 Major version id = 1 Minor version id = 0

6. The procedure might ask you for the date and time. Enter the date and time using the 24-hour clock format and press Return. For example:

   PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-MAY-1998 15:00

7. The procedure displays a list of the local devices on your system and, if you have them, HSC and MSCP-served devices. For example:

   Available device DUA0: device type Generic_DU Available device MUA0: device type TK50

8. When standalone BACKUP finishes booting, it displays an identification message followed by the dollar sign prompt ($):

   %BACKUP-I-IDENT, standalone BACKUP V7.2; the date is 19-MAY-1998 15:50 $

9. Remove the tape cartridge containing standalone BACKUP from the tape cartridge drive.
   To make a backup copy of the system disk, see Section 10.17.3.
   To restore the system disk, see Section 10.17.4.

	privacy and legal statement
6017PRO_049.HTML