HP Archive Backup System for OpenVMS Guide to Operations

More documents

Recommendations

Info

Saving and Restoring Data 3.4 Environments environment prologue and epilogue procedures operations to the individual save and restore prologue and epilogue procedures, which are executed before and/or after each file or disk specification in the save or restore request. The order of execution is illustrated below: • Environment prologue • Start save or restore request • First disk/file specification prologue • First disk/file specification save or restore operation • First disk/file specification epilogue • Next disk/file specification prologue • Next disk/file specification save or restore operation • Next disk/file specification epilogue • ...... • End save or restore request • Environment epilogue (only on successful completion) ABS defines logical names that can be used within the prologue or epilogue command procedure. These are defined in the process job table as follows: Table 3–1 Logical Names Available to Environment Prologues and Epilogues Logical Name ABS_SAVE_REQUEST_NAME ABS_RESTORE_REQUEST_NAME ABS_STORAGE_CLASS ABS_EXECUTION_ENVIRONMENT ABS_NODE_NAME ABS_OUTPUT_DEVICE Meaning Name of the save request Name of the restore request Name of the archive Name of the environment Execution node name The name of output device, or devices, used by the save or restore request. You should enter an OpenVMS command of up to 80 characters in the prologue and/or epilogue strings. For example: @ABS$SYSTEM:ABS_ENV_PROLOGUE.COM By default, there are no prologues or epilogues defined for an environment. 3.4.7 Retry Limit and Interval The retry limit and retry interval options allows you to specify the number of times and how often ABS should retry a object in a save or restore request before operator intervention is required. Specify the following: • Retry Limit - The number of retries (excluding the first attempt) to attempt before activating the notification options. A value of zero means no retries. You can also specify no limit, which means retries will be performed until the request either succeeds, or is manually stopped. 3-14 Saving and Restoring Data
Saving and Restoring Data 3.4 Environments • Interval - The interval between retry attempts, expressed as a delta time. The default retry interval is 15 minutes. Each time a retry attempt is made, ABS generates a warning message. If you wish to see the warning messages, select the warning option in the when attribute for notification. 3.4.8 Links Only and Span Filesystems 3.4.9 Listing Option 3.4.10 Lock 3.4.11 Notification For UNIX clients, ABS provides the option to either backup UNIX symbolic links only, or to follow the UNIX symbolic links and backup up the data as well. The default is to backup the symbolic links only (not the data). In addition, ABS allows you to backup only the root file system (such as the disk the root directory resides on) or an entire file system if the filesystem spans physical devices. The default is nospan filesystems, which copies the root file system only. Both attributes apply to data type UNIX_FILES only. The listing option allows you to specify the type of listing generated for save and restore requests using this environment. Specify one of the following options: • NONE - Does not generate a listing file • BRIEF - Generates a brief listing file • FULL - Generates a detailed listing file If not specified, NONE is the default option. ABS allows you to specify what a save request should do when data usage conflicts occur by means of the lock attribute. If you specify lock, ABS saves the data even if other applications have the data locked for write access. If you specify nolock ABS does not save the data if other applications have the data locked for write - this is the safer approach. If you specify lock, it is possible that the data you save is inconsistent, as the other application may be writing to the file during the actual save operation. Use lock with caution. The default is nolock. ABS uses the notification attributes in the environment to determine who, how and under what circumstances users are notified of ABS events during save and restore operations. ABS supports notification using mail, OPCOM or both. You can specify up to 32 separate notification options in each environment, using the following attributes: • MAIL - Specifies one or more mail users to be notified on certain types of event; specify one or more OpenVMS mail usernames (including node names as needed). • OPCOM - Specifies one or more OPCOM classes to be notified on certain types of events - specify one or more OpenVMS OPCOM classes (e.g. TAPES) to be notified - notification will be directed to the (execution) node(s) specified in the save or restore request. • TYPE - Indicates the level of information given. Select one of the following: – BRIEF - Contains only basic information (default) – NORMAL - Contains a moderate amount of information – FULL - Contains the maximum amount of information • WHEN - Indicates when the notification should occur. Choose one or more of the following: – START - Sends notification at the start of a save or restore request Saving and Restoring Data 3–15
Page 1 and 2: HP Archive Backup System for OpenVM
Page 3 and 4: Contents Preface . . . . . . . . .
Page 5 and 6: 3.6.1 Agent Qualifiers . . . . . .
Page 7 and 8: 4.11.7 Previous and Next Volumes .
Page 9 and 10: 9.3 Defining the Logical MDMS$SBT_T
Page 11 and 12: B.2 SLS/MDMS V2.x to ABS/MDMS V4.x
Page 13: Tables Table 3-1 Logical Names Avai
Page 17 and 18: Preface Intended Audience This docu
Page 19 and 20: 1 Introduction The Archive Backup S
Page 21 and 22: 2 Overview This chapter provides an
Page 23 and 24: Overview 2.2 ABS Objects Figure 2-1
Page 25 and 26: 2.2.6 Schedules 2.3 ABS Catalogs Ov
Page 27 and 28: Overview 2.5 Media, Device and Mana
Page 29 and 30: 2.8.3 Groups 2.8.4 Jukeboxes Overvi
Page 31 and 32: 2.8.8 Nodes 2.8.9 Pools 2.8.10 Volu
Page 33 and 34: 3 Saving and Restoring Data 3.1 Arc
Page 35 and 36: 3.1.5 Destination 3.1.6 Drives 3.1.
Page 37 and 38: 3.1.12 Volume Sets Saving and Resto
Page 39 and 40: 3.2.5 Staging 3.2.6 Catalog Save En
Page 41 and 42: • Save Type - Copied from related
Page 43 and 44: Example 3-4 Staging Information in
Page 45: 3.4.3 Compression 3.4.4 Data Safety
Page 49 and 50: Saving and Restoring Data 3.5 Saves
Page 53 and 54: Table 3-3 Disk, File, Path and Data
Page 59 and 60: • First disk/file specification p
Page 61 and 62: 3.5.17.1 HOLIDAYS.DAT Record Format
Page 63 and 64: Saving and Restoring Data 3.6 Selec
Page 65 and 66: 3.7.2 Command 3.7.3 Restriction Sav
Page 67: 3.7.5 Include and Exclude 3.7.6 Tim
Page 70 and 71: Media Management 4.2 Domain 4.2.1 A
Page 72 and 73: Media Management 4.2 Domain 4.2.15
Page 74 and 75: Media Management 4.3 Drives 4.3.5 D
Page 76 and 77: Media Management 4.3 Drives 4.3.15
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:
Page 113 and 114:
Figure 6-5 Domain View Showing Expa
Page 115 and 116:
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 and 128:
7.2 Prolog and Epilog Procedure Pre
Page 129 and 130:
7.2.1 Restoring The System Disk To
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:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Virtual Library System (VLS) 10.3 Q
Page 176 and 177:
Architecture 11.1 The Server Proces
Page 178 and 179:
Architecture 11.2 Scheduler Interfa
Page 180 and 181:
Architecture 11.3 Catalogs Example
Page 182 and 183:
Architecture 11.4 Coordinator 11.4.
Page 184 and 185:
Troubleshooting 12.2 Media Manageme
Page 186 and 187:
Troubleshooting 12.2 Media Manageme
Page 188 and 189:
Troubleshooting 12.4 ABS Catalogs 1
Page 190 and 191:
Troubleshooting 12.5 Windows and Un
Page 192 and 193:
Troubleshooting 12.6 RDF (Remote De
Page 195 and 196:
A Configuration Example Getting ABS
Page 197 and 198:
Configuration Example * Magazine -
Page 199 and 200:
Configuration Example Configuring s
Page 201 and 202:
Configuration Example If you comple
Page 203 and 204:
Configuration Example Assist: YES C
Page 205 and 206:
B Migrating from SLS/MDMS V2.X to A
Page 207 and 208:
Migrating from SLS/MDMS V2.X to ABS
Page 209 and 210:
Table B-1 SBK Symbols in ABS Termin
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
$ WRITE EpilogComFile - Migrating f
Page 245 and 246:
Table B-6 Execution Environment Par
Page 247 and 248:
• SAVE Migrating from SLS/MDMS V2
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Solution - Follow these steps: Migr
Page 257 and 258:
C Prev3 Support Prev3 Support is pr
Page 259 and 260:
Prev3 Support C.2 Using SLS as the
Page 261:
Prev3 Support C.2 Using SLS as the
Page 264 and 265:
Upgrading from ABS V2.X/V3.X to V4.
Page 266 and 267:
Upgrading from ABS V2.X/V3.X to V4.
Page 268 and 269:
ABS/MDMS Support for Fibre Channel
Page 270 and 271:
ABS/MDMS Support for Fibre Channel
Page 273 and 274:
Index Numerics 100 times per day 3-
Page 275 and 276:
MDMS$SBT_ ARCHIVE_n 9-20 MDMS$SBT_
Page 277:
volumes 3-4 W WARNING 3-14, 3-31 WE
show all

HP Archive Backup System for OpenVMS Guide to Operations

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?