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
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 51 and 52: Saving and Restoring Data 3.5 Saves
- Page 53 and 54: Table 3-3 Disk, File, Path and Data
- Page 55 and 56: Saving and Restoring Data 3.5 Saves
- Page 57 and 58: Saving and Restoring Data 3.5 Saves
- 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
Saving and Res<strong>to</strong>ring Data<br />
3.4 Environments<br />
• Interval - The interval between retry attempts, expressed as a delta time. The default retry<br />
interval is 15 minutes.<br />
Each time a retry attempt is made, ABS generates a warning message. If you wish <strong>to</strong> see the<br />
warning messages, select the warning option in the when attribute <strong>for</strong> notification.<br />
3.4.8 Links Only and Span Filesystems<br />
3.4.9 Listing Option<br />
3.4.10 Lock<br />
3.4.11 Notification<br />
For UNIX clients, ABS provides the option <strong>to</strong> either backup UNIX symbolic links only, or <strong>to</strong><br />
follow the UNIX symbolic links and backup up the data as well. The default is <strong>to</strong> backup the<br />
symbolic links only (not the data).<br />
In addition, ABS allows you <strong>to</strong> backup only the root file system (such as the disk the root direc<strong>to</strong>ry<br />
resides on) or an entire file system if the filesystem spans physical devices. The default is<br />
nospan filesystems, which copies the root file system only.<br />
Both attributes apply <strong>to</strong> data type UNIX_FILES only.<br />
The listing option allows you <strong>to</strong> specify the type of listing generated <strong>for</strong> save and res<strong>to</strong>re requests<br />
using this environment. Specify one of the following options:<br />
• NONE - Does not generate a listing file<br />
• BRIEF - Generates a brief listing file<br />
• FULL - Generates a detailed listing file<br />
If not specified, NONE is the default option.<br />
ABS allows you <strong>to</strong> specify what a save request should do when data usage conflicts occur by<br />
means of the lock attribute. If you specify lock, ABS saves the data even if other applications<br />
have the data locked <strong>for</strong> write access. If you specify nolock ABS does not save the data if other<br />
applications have the data locked <strong>for</strong> write - this is the safer approach. If you specify lock, it is<br />
possible that the data you save is inconsistent, as the other application may be writing <strong>to</strong> the file<br />
during the actual save operation. Use lock with caution. The default is nolock.<br />
ABS uses the notification attributes in the environment <strong>to</strong> determine who, how and under what<br />
circumstances users are notified of ABS events during save and res<strong>to</strong>re operations. ABS supports<br />
notification using mail, OPCOM or both. You can specify up <strong>to</strong> 32 separate notification<br />
options in each environment, using the following attributes:<br />
• MAIL - Specifies one or more mail users <strong>to</strong> be notified on certain types of event; specify<br />
one or more <strong>OpenVMS</strong> mail usernames (including node names as needed).<br />
• OPCOM - Specifies one or more OPCOM classes <strong>to</strong> be notified on certain types of events -<br />
specify one or more <strong>OpenVMS</strong> OPCOM classes (e.g. TAPES) <strong>to</strong> be notified - notification<br />
will be directed <strong>to</strong> the (execution) node(s) specified in the save or res<strong>to</strong>re request.<br />
• TYPE - Indicates the level of in<strong>for</strong>mation given. Select one of the following:<br />
– BRIEF - Contains only basic in<strong>for</strong>mation (default)<br />
– NORMAL - Contains a moderate amount of in<strong>for</strong>mation<br />
– FULL - Contains the maximum amount of in<strong>for</strong>mation<br />
• WHEN - Indicates when the notification should occur. Choose one or more of the following:<br />
– START - Sends notification at the start of a save or res<strong>to</strong>re request<br />
Saving and Res<strong>to</strong>ring Data 3–15