Document revision date: 15 July 2002

1. Mount the disk DUA2. The files will be restored to this disk.
2. Initialize DUA2:, effectively erasing any previous data on the disk. Restore the directory structure and all the files from the save set FULL_BACKUP.SAV to the disk DUA2. BACKUP restores the files contiguously on DUA2:, eliminating any disk fragmentation on that device.
   The /IMAGE qualifier restores a logical duplicate of the original disk so that the entire directory structure is restored and the files are placed in the proper directories.
3. Dismount the disk.

Restoring files after making an image backup and one or more incremental backups is a two-step process. First, restore the most recent image backup. Then, restore each subsequent incremental backup, starting with the most recent.

For the number of directory structure levels you can access see Section 11.14.1.

How to Perform This Task

To restore incremental backups, use the following procedure (note that the first few steps are similar to the procedure for restoring an image backup):

1. Mount the disk to which you will restore the files, using the MOUNT /FOREIGN command. (See Section 11.8.2 for information about the MOUNT command.)
2. Load the tape, disk, or diskette that contains the most recent image backup of the disk. If the backup save set spans more than one volume, load the first volume of the set. If the backup copy is on a disk or diskette, mount the volume.
3. If you do not know the name of the save set, perform one of the following actions:
   • If the save set is on a disk, make sure the disk is mounted and use the DIRECTORY command to determine the name of the save set. For example:

     $ DIRECTORY BACKUP_DISK:[BACKUPS] Directory SYS$SYSDEVICE:[BACKUPS] 19APRIL2000.SAV;1 Total of 1 file.

     
     The save set is named 19APRIL2000.SAV.

   • If the save set is on magnetic tape, load the tape and enter the following command, substituting the name of the tape drive you use for MIA0:

     $ BACKUP/LIST/REWIND MIA0: Listing of save set(s) Save set: 19APRIL2000.SAV Written by: SYSTEM UIC: [000001,000004] Date: 19-APR-2000 22:03:03.63 . . .

     
     The save set is named 19APRIL2000.SAV.

4. Enter the BACKUP command using the following syntax:

   BACKUP/IMAGE device:save-set-specifier[/SAVE_SET] output-specifier

   
   The /IMAGE qualifier indicates that you are restoring an image backup. If your backup copy is on a disk or diskette, then you must also use the /SAVE_SET qualifier immediately after the save-set specifier (device:save-set-specifier).

5. If your backup copy is on more than one tape or diskette, load each subsequent tape or diskette when BACKUP prompts for the next volume.
6. Use the /NOUNLOAD qualifier to dismount the disk onto which you have just restored the files from the image backup.
7. Mount the disk that you are restoring as a file-structured volume, using the following syntax:

   MOUNT device-name: volume-label

   
   The parameter device-name is the name of the drive that holds the volume you want to mount. The parameter volume-label is the 1- to 6-character alphanumeric identification you assigned to the volume with the INITIALIZE command.

8. Dismount the media that contained the image backup and mount the tape, disk, or diskette that contains the most recent incremental backup of the disk.
9. Restore your incremental save sets, beginning with the most recent backup. Use the following syntax to restore an incremental backup:

   BACKUP/INCREMENTAL save-set-specifier[/SAVE_SET] device-specifier

   
   Remember that you must use the /SAVE_SET qualifier after the save-set specifier if your backup copies are on a disk or diskette.
   Continue restoring the incremental backups, from the most recent to the oldest, until you have processed all of the incremental backups since the most recent image backup. If the incremental backups are on more than one tape, diskette, or disk, then you must load each one successively when prompted by BACKUP.
   When you have processed the oldest incremental backup, the restore operation is complete.

Example

The next example shows the process of restoring an entire disk after a series of incremental backups, using the following elements and assumptions:

• The save set for the image backup is named WORK_BACKUP.SAV. This save set was created using the BACKUP/IMAGE/RECORD command.
• The save sets for the incremental backups are named as follows:

  WORK_16_JAN.SAV
  WORK_17_JAN.SAV
  WORK_18_JAN.SAV

• Both the image and the incremental backup save sets are on the disk named DUA3:, which is already mounted.
• The disk to which the files will be restored is named DUA2.

$ MOUNT/FOREIGN DUA2:(1) %MOUNT-I-MOUNTED, WORK_B mounted on _DUA2: $ BACKUP/IMAGE DUA3:WORK_BACKUP.SAV/SAVE_SET DUA2:(2) $ DISMOUNT/NOUNLOAD DUA2:(3) $ MOUNT DUA2: WORK_B (4) %MOUNT-I-MOUNTED, WORK_B mounted on _DUA2: $ BACKUP/INCREMENTAL DUA3:WORK_18_JAN.SAV/SAVE_SET DUA2:(5) $ BACKUP/INCREMENTAL DUA3:WORK_17_JAN.SAV/SAVE_SET DUA2:(6) $ BACKUP/INCREMENTAL DUA3:WORK_16_JAN.SAV/SAVE_SET DUA2:(7)

In this example, the individual command lines perform the following steps:

1. Mount the disk DUA2: with the /FOREIGN qualifier. The files will be restored to this disk.
2. Restore the directory structure and all the files from the save set WORK_BACKUP.SAV to the disk DUA2. This was an image backup, so it must be the first save set you restore when you want to restore incremental backup save sets.
3. Logically dismount the disk DUA2.
4. Remount the disk DUA2:, this time as a Files--11 volume.
5. Restore the most recent incremental backup.
6. Restore the next incremental backup.
7. Restore the oldest incremental backup.
   Restoring the incremental backups in reverse chronological order is the most efficient way to restore files. When you have restored the last incremental backup, the restore operation is complete.

BACKUP examines the target disk and the save-set contents to determine which save-set entries to ignore and which target disk entries to delete. If BACKUP encounters a privilege error when attempting to delete directories or other files from the target disk, BACKUP attempts to change the protection of the files so they can be deleted.

BACKUP detects modified directory files and will subsequently save the contents of the directory and its subdirectories to allow proper restoration of renamed directories.

BACKUP processes the target disk directory structure by directory levels, in alphabetical order. Thus, circumstances can occur that prevent BACKUP from correctly restoring an incremental save set to a target disk. For example, the target disk does not have sufficient space to hold newly "renamed" directories and their contents prior to deleting the original directories and their contents on the target disk.

If incremental restore fails due to insufficient disk space, a possible solution is to apply the incremental save set a second time (before doing anything else). This causes the first incremental restore to continue and delete directories and their contents, making more space available on the target disk. A second solution is to selectively restore files from the save set.

BACKUP attempts to restore alias or synonym file entries in incremental restore operations that do not specify multiple processing of alias or synonym file entries (/NOALIAS). In cases where the alias entry cannot be restored properly, BACKUP issues an error message indicating the alias file entry, its primary file, and a secondary status of the cause of the failure.

If you specify the /LOG qualifier, then BACKUP issues a message upon successful restoration of alias file entries.

If you specify the /VERIFY qualifier, BACKUP attempts alias entry restoration during the verify pass. Otherwise, alias entry restoration is attempted along with the normal file restoration. The reason for this behavior is that BACKUP attempts to restore all primary files before attempting to restore alias entries that will eventually reference those files.

11.16.3 Restoring Volume Shadow Sets

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

11.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 11.17.3.
   To restore the system disk, see Section 11.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.3 Major version id = 3 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) 2000 Compaq Computer Corporation. All rights reserved. $set noverify Copyright © (c) 2000 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. $$$

11.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 11-8 lists the qualifiers that you can use with standalone BACKUP.

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

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

	privacy and legal statement
6017PRO_051.HTML