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
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration Environment Parameter SBK Equivalent Meaning ACL Identifies access to the Environment Data Safety QUALIFIERS Bitmask that contains the data safety options to be applied during the backup. Data safety options include CRC checking and full data verification. Listing Option LISTING_GEN FULL Determines whether a listing file is produced and if it is a “FULL” or a “BRIEF” listing. Span Filesys Opt. For UNIX type of file systems, determines whether the entire file system is backed up, even if it spreads across multiple physical devices. Links Only For UNIX type of file systems, determines whether ABS takes backup of only the logical links or the data as well. Compression For UNIX type of file systems, determines the type of compression to be applied on the savesets. Action QUALIFIERS Determines the action to be taken on the original data objects (example - on the files backed up). Options include None, Record Backup Date, or Delete. Profile PRIVS Determines the username, privileges and access rights used during the backup operation. The special keyword “” indicates that the backup operations must be performed with the username, privileges and access rights of the person issuing the ABS SAVE command. Notification REPLY_MSG STATUS_MAIL Determines when and how the notification is created, and also the operator who is notified. Locking Option QUALIFIERS Determines the extent to which the inter-locking is done between the backup in progress and an active file system. Options include Ignore File Writers and Hot Backup. Drive Count N_DRIVES Determines the number of tape drives to be used during the backup operations. Retry Count Determines how many times a failed backup must be retried. Interval Determines how often a failed backup must be retried. Prologue Command Epilogue Command PRE_PROCESS_FI RST POST_PROCESS_ LAST Command that must be executed when the backup starts, contrast to the Save request Prologue. Command that must be executed when the backup completes, contrast to the Save request Epilogue. B–46 Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration Table B–9 ABS Save Request Parameter and SLS SBK Equivalent Save Request Parameter SBK Equivalent Meaning Name SBK File name Identifies the group of backup operations to be performed. Type of Save QUALIFIERS Determines the type of backup executed; whether it is Full, Incremental or Selective (individual file) backup. Source Node NODE_n Identifies the Node where the data resides. Include Spec (Include Specification) FILES_n Identifies the data to be backed up. Multiple include specifications can be given on a single Save request, and each can have a different Object Type. Object Type BACKUP_TYPE Identifies the type of data to be backed up. ABS supports different data types. Some of them include OpenVMS Files, UNIX Files, and Oracle RDB Databases. Agent Qual. (Agent Qualifiers) QUALIFIERS Allows backup agent specific qualifiers to be added to the command that is used to take data backup. Since Date QUALIFIERS Determines if data objects to be backed up must be selected based on creation/modification date. Before Date QUALIFIERS Determines if data objects to be backed up must be selected based on creation/modification date. Exclude Specification QUALIFIERS Determines selected data objects to be excluded from the backup. Storage Class (Archive) Name Provides the Storage Class name into which the data is backed up. Environment Provides the name of the Execution Environment that needs to be used for the backup operations. Start Time TIME_n Indicates the time at which the Save request must start each time it is scheduled for taking backups. Note that an SBK can provide multiple DAYS_n and TIME_n parameters but an ABS Save request is restricted to a single Start Time and Interval. Scheduling Interval Explicit Interval DAYS_n DAYS_n Identifies the repeat interval for the Save request. ABS provides a variety of predefined simple inter vals, such as Daily, Weekly, Monthly, as well as several “complex” intervals, such as Weekly Full with Daily Incremental, and log based schedules. See the information on "Log-n Backup Schedules" in ABS for a full description of log based schedules. Prologue Command Epilogue Command PRE_PROCESS_E ACH POST_PROCESS_ EACH Command that must be executed before each backup operation within the Save request starts, contrast to the Environment’s Prologue. Command that must be executed after each backup operation within the Save request completes, contrast to the Environment’s Epilogue. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–47
- 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: Migrating from SLS/MDMS V2.X to ABS
- Page 213 and 214: Migrating from SLS/MDMS V2.X to ABS
- Page 215 and 216: Migrating from SLS/MDMS V2.X to ABS
- Page 217 and 218: Migrating from SLS/MDMS V2.X to ABS
- Page 219 and 220: Migrating from SLS/MDMS V2.X to ABS
- Page 221 and 222: Migrating from SLS/MDMS V2.X to ABS
- Page 223 and 224: Migrating from SLS/MDMS V2.X to ABS
- Page 225 and 226: Migrating from SLS/MDMS V2.X to ABS
- Page 227 and 228: Migrating from SLS/MDMS V2.X to ABS
- Page 229 and 230: Migrating from SLS/MDMS V2.X to ABS
- Page 231 and 232: Migrating from SLS/MDMS V2.X to ABS
- Page 233 and 234: Migrating from SLS/MDMS V2.X to ABS
- Page 235 and 236: Migrating from SLS/MDMS V2.X to ABS
- Page 237 and 238: Migrating from SLS/MDMS V2.X to ABS
- Page 239 and 240: Migrating from SLS/MDMS V2.X to ABS
- Page 241 and 242: Migrating from SLS/MDMS V2.X to ABS
- 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: Migrating from SLS/MDMS V2.X to ABS
- Page 253 and 254: Migrating from SLS/MDMS V2.X to ABS
- 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
Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X<br />
B.2 SLS/MDMS V2.x <strong>to</strong> ABS/MDMS V4.x Migration<br />
Environment<br />
Parameter<br />
SBK Equivalent<br />
Meaning<br />
ACL Identifies access <strong>to</strong> the Environment<br />
Data Safety QUALIFIERS Bitmask that contains the data safety options <strong>to</strong> be<br />
applied during the backup. Data safety options<br />
include CRC checking and full data verification.<br />
Listing Option<br />
LISTING_GEN<br />
FULL<br />
Determines whether a listing file is produced and if<br />
it is a “FULL” or a “BRIEF” listing.<br />
Span Filesys Opt. For UNIX type of file systems, determines whether<br />
the entire file system is backed up, even if it spreads<br />
across multiple physical devices.<br />
Links Only For UNIX type of file systems, determines whether<br />
ABS takes backup of only the logical links or the<br />
data as well.<br />
Compression For UNIX type of file systems, determines the type<br />
of compression <strong>to</strong> be applied on the savesets.<br />
Action QUALIFIERS Determines the action <strong>to</strong> be taken on the original<br />
data objects (example - on the files backed up).<br />
Options include None, Record <strong>Backup</strong> Date, or<br />
Delete.<br />
Profile PRIVS Determines the username, privileges and access<br />
rights used during the backup operation. The special<br />
keyword “” indicates that the<br />
backup operations must be per<strong>for</strong>med with the username,<br />
privileges and access rights of the person<br />
issuing the ABS SAVE command.<br />
Notification<br />
REPLY_MSG<br />
STATUS_MAIL<br />
Determines when and how the notification is created,<br />
and also the opera<strong>to</strong>r who is notified.<br />
Locking Option QUALIFIERS Determines the extent <strong>to</strong> which the inter-locking is<br />
done between the backup in progress and an active<br />
file system. Options include Ignore File Writers and<br />
Hot <strong>Backup</strong>.<br />
Drive Count N_DRIVES Determines the number of tape drives <strong>to</strong> be used<br />
during the backup operations.<br />
Retry Count Determines how many times a failed backup must<br />
be retried.<br />
Interval Determines how often a failed backup must be<br />
retried.<br />
Prologue Command<br />
Epilogue Command<br />
PRE_PROCESS_FI<br />
RST<br />
POST_PROCESS_<br />
LAST<br />
Command that must be executed when the backup<br />
starts, contrast <strong>to</strong> the Save request Prologue.<br />
Command that must be executed when the backup<br />
completes, contrast <strong>to</strong> the Save request Epilogue.<br />
B–46 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X
Change language