[Digital logo]
[HR]

OpenVMS System Manager's Manual


Previous | Contents

The following example shows how to restore an image backup, using the following assumptions:

$ MOUNT/FOREIGN DRA2: (1)
%MOUNT-I-MOUNTED, DISK1 mounted on _DRA2:
$ BACKUP/IMAGE  MIA1:FULL_BACKUP.SAV/REWIND  DRA2: (2)
$ DISMOUNT/NOUNLOAD  DRA2: (3)
 

In this example, the individual command lines do the following:

  1. Mount the disk DRA2. The files will be restored to this disk. The disk must be loaded before it can be mounted.
  2. Initialize DRA2:, 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 DRA2. BACKUP restores the files contiguously on DRA2:, 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.

10.16.2 Restoring Incremental Backups

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 10.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 10.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, do one of the following:
  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 following example shows the process of restoring an entire disk after a series of incremental backups, using the following elements and assumptions:

    $ 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 do the following:

    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.

    10.16.2.1 Restoring to Target Disk Structures

    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.


    Note

    Renaming directories is not recommended. Also, changing security information for a directory changes its modification date. Thus, a directory might appear to be "renamed" and its contents included in incremental save sets if the file protection or security information is changed. The addition of renamed directory contents might increase the size of some incremental save sets.

    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.

    10.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, see Volume Shadowing for OpenVMS.


    Note

    Because the BACKUP output device (the shadow set) must be mounted using the /FOREIGN qualifier, Digital does not support a restore operation from an image save set to a virtual unit.

    10.17 Backing Up and Restoring the System Disk

    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.


    Note

    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.

    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.

      10.17.1.1 Example

      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.1 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) 1996 Digital Equipment Corporation.  All rights reserved. 
      $set noverify 
       
       
       
          Copyright © (c) 1996 Digital Equipment 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 See the OpenVMS System Management Utilities Reference Manual
      /LIST[=file-spec] See 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 See the OpenVMS System Management Utilities Reference Manual
      /BY_OWNER=uic See the OpenVMS System Management Utilities Reference Manual
      /COMMENT=string None
      /[NO]CRC /CRC
      /DENSITY=n See the OpenVMS System Management Utilities Reference Manual
      /[NO]EXACT_ORDER /NOEXACT_ORDER
      /GROUP_SIZE=n /GROUP_SIZE=10
      /LABEL=(string[,...]) See the OpenVMS System Management Utilities Reference Manual
      /PROTECTION[=(code)] See 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. 
        

      10.17.2.2 Booting Standalone BACKUP from a Disk (VAX Only)

      To boot standalone BACKUP from a disk, do the following:

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

        10.17.2.3 Building Standalone BACKUP on a Tape Cartridge (VAX Only)

        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, do the following:

        1. Obtain a blank, initialized tape cartridge. Write the name S/A BKUP V7.1 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.1 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:
          Ending time   19-MAY-1996 16:44:29.90 
          Starting time 19-MAY-1996 16:30:39.05       
           
          The Kit is complete. 
                   
           
          $ 
          
        11. Remove the tape cartridge labeled S/A BKUP V7.1 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.

        10.17.2.4 Booting Standalone BACKUP from a Tape Cartridge (VAX Only)

        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.1 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-1996 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.1; the date is 19-MAY-1996 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.

        10.17.3 Backing Up the System Disk to Tape

        When backing up your system disk, you must understand the functions of the /IMAGE and /PHYSICAL qualifiers to the BACKUP command before using standalone BACKUP:
        Qualifier Function
        /IMAGE Lets you create a functionally equivalent copy of the entire system disk. When restored, files from an image backup are placed contiguously on the system disk, eliminating disk fragmentation.
        /PHYSICAL Copies, saves, restores, or compares the entire system disk in terms of logical blocks, ignoring any file structure.


        Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

        [HR]

          6017P033.HTM
          OSSG Documentation
          22-NOV-1996 14:22:04.51
        

        Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

        Legal