HP Archive Backup System for OpenVMS Guide to Operations
HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations
Preparing For Disaster Recovery 7.2 Prolog and Epilog Procedure $! $ NextObject: $! $ VolSetLog = "ABS_OS_VOLUME_SET_''n'" $ VolRVNLog = "ABS_OS_START_RVN_''n'" $ ObjectLog = "ABS_OS_OBJECT_SET_''n'" $ SavsetLog = "ABS_OS_SAVESET_NAME_''n'" $ CALL GetVolumeList "''F$TRNLNM(VolSetLog)'" 'F$TRNLNM(VolRVNLog)' VolumeList $ Destination = "''F$TRNLNM(ObjectLog)'" $ Destination = F$EXTRACT(0,F$LOCATE(":",Destination),Destination) $ Destination = "''F$TRNLNM(Destination)'" $ IF F$LOCATE(".]",Destination).NE.F$LENGTH(Destination) $ THEN $ Destination = Destination + "[...]" - "][" $ ELSE $ Destination = Destination + "[*...]" $ ENDIF $ WRITE SYS$OUTPUT " $ BACKUP/OVERLAY/EXACT_ORDER/NOASSIST -" $ WRITE SYS$OUTPUT " _$ tape:","''F$TRNLNM(Savset- Log)'/LABEL=(",VolumeList, $ WRITE SYS$OUTPUT " _$ ''Destination'" $ WRITE SYS$OUTPUT "." $ n = n + 1 $ IF n.LE.nmax THEN GOTO NextObject $ WRITE SYS$OUTPUT "." $ WRITE SYS$OUTPUT "After restoring the savesets rename the MDMS database" $ WRITE SYS$OUTPUT "files from ""MDMS$*_DB.DAT_COPY"" to ""*.DAT""/NEW_VERSION." $ WRITE SYS$OUTPUT "." $ EXIT $! $ GetVolumeList: SUBROUTINE $! $ VolumeID = "''P1'" $ RVN = 'P2' $ 'P3' == "" $ VolumeRVN = 1 $! $ NextVolume: $! $ MDMS SHOW VOLUME 'VolumeID'/SYMBOL $ IF VolumeRVN.GE.RVN $ THEN $ IF 'P3'.NES."" THEN 'P3' == 'P3' + "," $ 'P3' == 'P3' + "''MDMS_INQ_VOLUME_ID'" $ ENDIF $ IF "''MDMS_INQ_NEXT_VOLUME'".EQS."" THEN GOTO EndVolumeList $ VolumeID = "''MDMS_INQ_NEXT_VOLUME'" $ VolumeRVN = VolumeRVN + 1 $ GOTO NextVolume $! $ EndVolumeList: $! $ EXIT The example procedure creates copies of the MDMS database files in the prolog phase. This allows to save the files in a consistent state. After a restore from the saveset the files need to be renamed to their original names. For convenience the procedure prints out the backup commands needed to restore the data using information in logical names defined by ABS during the save operation. 7-6 Preparing For Disaster Recovery
7.2.1 Restoring The System Disk To restore your system disk you need to use Standalone BACKUP. Preparing For Disaster Recovery 7.2 Prolog and Epilog Procedure • For Alpha systems, see the section "Backing Up the System Disk" in the Appendix of the “Alpha Upgrade and Installation Manual” in the OpenVMS Documentation. • For VAX systems see the chapter “Using BACKUP” in the “System Manager’s Manual” in the OpenVMS Documentation. Use the information from the ABS save log to specify the parameters for the BACKUP command line: a. /LABEL=(volume_1,volume_2,...volume_n) - the volume IDs of the tapes being used b. The saveset name c. The target disk d. /IMAGE/NOASSIST qualifiers Example 7–5 BACKUP Command to Restore the System Disk $ BACKUP/IMAGE MKA500:24DEC20012359590./LABEL=(GKF011,GKF022) - _$DGA100:/NOASSIST This restores an image of your system disk in saveset “24DEC20012359590.” on tape volumes “GKF011” and “GKF022” to disk device “DGA100”. After a successful restore, boot from your restored system disk. If your system does not boot all the way through you may have to disable the execution of your “SYSTARTUP_VMS.COM” command procedure by using a conversational boot and renaming the file. 7.2.2 Restoring Remaining Savesets Once your system is up-and-running you can restore other save sets necessary to complete the disaster recovery: Make sure that all of these components or products are shut down before you restore the individual files. Use the following restore order: 1. First, any other product required by ABS, such as your 3rd party scheduler data if it has been saved separately. You should startup the component or product just restored. 2. Restore MDMS$ROOT if it has been saved separately. After the restore rename the “MDMS$*_DB.DAT_COPY” files to “*.DAT”. You can startup MDMS now. 3. Restore ABS$ROOT if it has been saved separately. Restore any other save used to save the catalog files which are located outside of ABS$ROOT. After the restore you can startup ABS. Use the information from the ABS save log to specify the parameters for the BACKUP command lines: a. /LABEL=(volume_1,volume_2,...volume_n) - the volume IDs of the tapes being used b. The saveset name c. The target disk d. /IMAGE/NOASSIST qualifiers Preparing For Disaster Recovery 7–7
- Page 78 and 79: Media Management 4.5 Jukeboxes 4.5.
- Page 80 and 81: Media Management 4.5 Jukeboxes 4.5.
- Page 82 and 83: Media Management 4.7 Magazines 4.6.
- Page 84 and 85: Media Management 4.8 Media Types 4.
- Page 86 and 87: Media Management 4.11 Volumes 4.10.
- Page 88 and 89: Media Management 4.11 Volumes Table
- Page 90 and 91: Media Management 4.11 Volumes 4.11.
- Page 92 and 93: Media Management 4.11 Volumes neede
- Page 94 and 95: Media Management 4.11 Volumes • R
- Page 96 and 97: Media Management 4.11 Volumes 4.11.
- Page 99 and 100: 5 Security The security model used
- Page 101 and 102: Security 5.1 MDMS Rights Table 5-1
- Page 103 and 104: Table 5-4 Domain Access Control Opt
- Page 105 and 106: 6 User Interfaces ABS and MDMS supp
- Page 107 and 108: 6.1.3 Logging In User Interfaces 6.
- Page 109 and 110: User Interfaces 6.1 Graphical User
- Page 111 and 112: User Interfaces 6.1 Graphical User
- Page 113 and 114: Figure 6-5 Domain View Showing Expa
- Page 115 and 116: User Interfaces 6.1 Graphical User
- Page 117 and 118: 6.1.13 Viewing MDMS Audit and Event
- Page 119 and 120: 6.2.1 Syntax Overview User Interfac
- Page 121 and 122: User Interfaces 6.3 User Interface
- Page 123 and 124: 7 Preparing For Disaster Recovery I
- Page 125 and 126: 7.1.2 Backup of MDMS$ROOT Preparing
- Page 127: 7.2 Prolog and Epilog Procedure Pre
- Page 131 and 132: 8 Remote Devices 8.1 RDF Installati
- Page 133 and 134: Remote Devices 8.4 Monitoring and T
- Page 135 and 136: 8.4.4 Changing Network Parameters f
- Page 137 and 138: • Free Space is 20 Remote Devices
- Page 139 and 140: Remote Devices 8.5 Controlling Acce
- Page 141: Remote Devices 8.7 RDF Error Messag
- Page 144 and 145: System Backup to Tape for Oracle Da
- Page 146 and 147: System Backup to Tape for Oracle Da
- Page 148 and 149: System Backup to Tape for Oracle Da
- Page 150 and 151: System Backup to Tape for Oracle Da
- Page 152 and 153: System Backup to Tape for Oracle Da
- Page 154 and 155: System Backup to Tape for Oracle Da
- Page 156 and 157: System Backup to Tape for Oracle Da
- Page 158 and 159: System Backup to Tape for Oracle Da
- Page 160 and 161: System Backup to Tape for Oracle Da
- Page 162 and 163: System Backup to Tape for Oracle Da
- Page 164 and 165: System Backup to Tape for Oracle Da
- Page 166 and 167: System Backup to Tape for Oracle Da
- Page 168 and 169: System Backup to Tape for Oracle Da
- Page 170 and 171: System Backup to Tape for Oracle Da
- Page 172 and 173: System Backup to Tape for Oracle Da
- Page 174 and 175: Virtual Library System (VLS) 10.3 Q
- Page 176 and 177: Architecture 11.1 The Server Proces
Preparing For Disaster Recovery<br />
7.2 Prolog and Epilog Procedure<br />
$!<br />
$ NextObject:<br />
$!<br />
$ VolSetLog = "ABS_OS_VOLUME_SET_''n'"<br />
$ VolRVNLog = "ABS_OS_START_RVN_''n'"<br />
$ ObjectLog = "ABS_OS_OBJECT_SET_''n'"<br />
$ SavsetLog = "ABS_OS_SAVESET_NAME_''n'"<br />
$ CALL GetVolumeList "''F$TRNLNM(VolSetLog)'" 'F$TRNLNM(VolRVNLog)'<br />
VolumeList<br />
$ Destination = "''F$TRNLNM(ObjectLog)'"<br />
$ Destination = F$EXTRACT(0,F$LOCATE(":",Destination),Destination)<br />
$ Destination = "''F$TRNLNM(Destination)'"<br />
$ IF F$LOCATE(".]",Destination).NE.F$LENGTH(Destination)<br />
$ THEN<br />
$ Destination = Destination + "[...]" - "]["<br />
$ ELSE<br />
$ Destination = Destination + "[*...]"<br />
$ ENDIF<br />
$ WRITE SYS$OUTPUT " $ BACKUP/OVERLAY/EXACT_ORDER/NOASSIST -"<br />
$ WRITE SYS$OUTPUT " _$ tape:","''F$TRNLNM(Savset-<br />
Log)'/LABEL=(",VolumeList,<br />
$ WRITE SYS$OUTPUT " _$ ''Destination'"<br />
$ WRITE SYS$OUTPUT "."<br />
$ n = n + 1<br />
$ IF n.LE.nmax THEN GOTO NextObject<br />
$ WRITE SYS$OUTPUT "."<br />
$ WRITE SYS$OUTPUT "After res<strong>to</strong>ring the savesets rename the MDMS<br />
database"<br />
$ WRITE SYS$OUTPUT "files from ""MDMS$*_DB.DAT_COPY"" <strong>to</strong><br />
""*.DAT""/NEW_VERSION."<br />
$ WRITE SYS$OUTPUT "."<br />
$ EXIT<br />
$!<br />
$ GetVolumeList: SUBROUTINE<br />
$!<br />
$ VolumeID = "''P1'"<br />
$ RVN = 'P2'<br />
$ 'P3' == ""<br />
$ VolumeRVN = 1<br />
$!<br />
$ NextVolume:<br />
$!<br />
$ MDMS SHOW VOLUME 'VolumeID'/SYMBOL<br />
$ IF VolumeRVN.GE.RVN<br />
$ THEN<br />
$ IF 'P3'.NES."" THEN 'P3' == 'P3' + ","<br />
$ 'P3' == 'P3' + "''MDMS_INQ_VOLUME_ID'"<br />
$ ENDIF<br />
$ IF "''MDMS_INQ_NEXT_VOLUME'".EQS."" THEN GOTO EndVolumeList<br />
$ VolumeID = "''MDMS_INQ_NEXT_VOLUME'"<br />
$ VolumeRVN = VolumeRVN + 1<br />
$ GOTO NextVolume<br />
$!<br />
$ EndVolumeList:<br />
$!<br />
$ EXIT<br />
The example procedure creates copies of the MDMS database files in the prolog phase. This<br />
allows <strong>to</strong> save the files in a consistent state. After a res<strong>to</strong>re from the saveset the files need <strong>to</strong> be<br />
renamed <strong>to</strong> their original names.<br />
For convenience the procedure prints out the backup commands needed <strong>to</strong> res<strong>to</strong>re the data using<br />
in<strong>for</strong>mation in logical names defined by ABS during the save operation.<br />
7-6 Preparing For Disaster Recovery