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 – . – . – Files_24:== Disk$User1:[Example]*.Com – . – . – . – Files_27:== Disk$User1:[Example1]*.Dat More than 27 include specifications are provided. • Qualifiers_n: – Qualifiers_n:== /Image ! Full backup After the DCL command procedure “Example2_ABS.COM” is executed, the following ABS Policy objects are created: • Archive class: Example2_ABS_SC • Environment: Example2_ABS_ENV • Save: – Example2_ABS_FULL_1 – Example2_ABS_FULL_2 Two Save requests are created for a single DCL command procedure to implement the Save Policy object. This is because in ABS, a Save request can have a maximum of 24 include specifications. The remaining include specifications are included in the subsequent Save request that is created. The first Save request “Example2_ABS_FULL_1” executes the backup for all the 24 include specifications. The next Save request “Example2_ABS_FULL_2” executes the backup for the remaining three include specifications. Note The conversion utility had a limit of 9 include specification for a single Save request. This limit is removed in ABS/MDMS T4.4 conversion utility to combine the 24 include specifications in a single Save request. Currently ABS/MDMS supports 24 include specifications in a Save request. B.2.4.3.8 ABS Policy Attributes in SBK Terminology – This section provides information on the ABS Policy objects’ parameters, their corresponding SBK Symbols and the meaning of those parameters. Refer to the following tables for better understanding of how the parameters are mapped to the respective Symbols in the SBK files. • Table B–7, “ABS Storage Class Parameter and SLS SBK Equivalent” lists the ABS Storage Class parameters and their equivalent SBK symbols. • Table B–8, “ABS Execution Environment Parameter and SLS SBK Equivalent” lists the ABS Execution Environment parameters and their equivalent SBK symbols. • Table B–9, “ABS Save Request Parameter and SLS SBK Equivalent” lists ABS Save request parameters and their equivalent SBK symbols. B–44 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–7 ABS Storage Class Parameter and SLS SBK Equivalent Storage Class Parameter SBK Equivalent Meaning Name CONTINUE Common name that can be referenced by multiple Save requests Archive Type Determines if the Storage Class is tape based (type is MDMS) or disk based (type is FILES- 11) Owner Determines the NODE::USER of the Storage Class owner. The owner will always have the CONTROL access. ACL PROTECTION Determines access to the backed up data. ABS provides full ACL based access. SLS only provides OpenVMS-style System, Owner, Group and World access. Tape Pool TAPE_POOL MDMS pool from where volumes are allocated for backups Type of Media MEDIA_TYPE MDMS media type to be allocated for backups Retain Value SCRATCH_DAYS Number of days the backed up data will be saved before the tapes are recycled. Note that a Save request can specify a retention shorter or equal to the value in the Storage Class. Consolidation CONTINUE Set of parameters that determine how the backup savesets will be consolidated onto tapes. For example, if the Consolidation Interval is set to seven days, savesets will be appended onto a volume set for seven days before a new volume set is created. Catalog HISTORY_SET Name of the catalog that stores data about the files that are backed up and their location Maximum Saves Number of simultaneous Save requests that can be written into the Storage Class. Also, determines the number of MDMS volume sets that are simultaneously active in the Storage Class. Media Location MDMS onsite location field to match when allocating volumes for backups. Drive List DRIVE_TYPE List of specific drives to be used for backup operations in the Storage Class. Normally, it must be managed through the MDMS drive objects. Table B–8 ABS Execution Environment Parameter and SLS SBK Equivalent Environment Parameter SBK Equivalent Meaning Name Identifies the Environment to be referenced by the Save requests Owner Identifies the owner for the Environment. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–45
- 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: 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: • SAVE Migrating from SLS/MDMS V2
- Page 251 and 252: 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 />
– .<br />
– .<br />
– Files_24:== Disk$User1:[Example]*.Com<br />
– .<br />
– .<br />
– .<br />
– Files_27:== Disk$User1:[Example1]*.Dat<br />
More than 27 include specifications are provided.<br />
• Qualifiers_n:<br />
– Qualifiers_n:== /Image ! Full backup<br />
After the DCL command procedure “Example2_ABS.COM” is executed, the following ABS<br />
Policy objects are created:<br />
• <strong>Archive</strong> class: Example2_ABS_SC<br />
• Environment: Example2_ABS_ENV<br />
• Save:<br />
– Example2_ABS_FULL_1<br />
– Example2_ABS_FULL_2<br />
Two Save requests are created <strong>for</strong> a single DCL command procedure <strong>to</strong> implement the Save Policy<br />
object. This is because in ABS, a Save request can have a maximum of 24 include specifications.<br />
The remaining include specifications are included in the subsequent Save request that is<br />
created. The first Save request “Example2_ABS_FULL_1” executes the backup <strong>for</strong> all the 24<br />
include specifications. The next Save request “Example2_ABS_FULL_2” executes the backup<br />
<strong>for</strong> the remaining three include specifications.<br />
Note<br />
The conversion utility had a limit of 9 include specification <strong>for</strong> a single Save request.<br />
This limit is removed in ABS/MDMS T4.4 conversion utility <strong>to</strong> combine the 24 include<br />
specifications in a single Save request. Currently ABS/MDMS supports 24 include<br />
specifications in a Save request.<br />
B.2.4.3.8 ABS Policy Attributes in SBK Terminology –<br />
This section provides in<strong>for</strong>mation on the ABS Policy objects’ parameters, their corresponding<br />
SBK Symbols and the meaning of those parameters. Refer <strong>to</strong> the following tables <strong>for</strong> better<br />
understanding of how the parameters are mapped <strong>to</strong> the respective Symbols in the SBK files.<br />
• Table B–7, “ABS S<strong>to</strong>rage Class Parameter and SLS SBK Equivalent” lists the ABS S<strong>to</strong>rage<br />
Class parameters and their equivalent SBK symbols.<br />
• Table B–8, “ABS Execution Environment Parameter and SLS SBK Equivalent” lists the<br />
ABS Execution Environment parameters and their equivalent SBK symbols.<br />
• Table B–9, “ABS Save Request Parameter and SLS SBK Equivalent” lists ABS Save<br />
request parameters and their equivalent SBK symbols.<br />
B–44 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X