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 B.2.4.3.3 Command Syntax – $ @ABS$SYSTEM:SLS_CONVERT [] […] This parameter identifies the set of SBK files to be converted by this command. The string given must not include SLS$SYSBAK: or the _SBK.COM suffix. For example, if you want to convert the SBK file “SLS$SYSBAK:Example*_SBK.COM”, you must issue the command: $ @ABS$SYSTEM:SLS_CONVERT Example* … These optional parameters allow you to search the SBK files defined by the and only process those files that contain all the given strings. Since the SLS_CONVERT command procedure uses a /MATCH=AND on the Search command, the strings must all appear on the same line in the SBK file. Sample Conversion – $ @ABS$SYSTEM:SLS_CONVERT * Building list of SBK's from SLS$SYSBAK:*_SBK.COM;0 Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example1_SBK.COM;1... Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example2_SBK.COM;1... Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example3_SBK.COM;1... Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example4_SBK.COM;1... Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example5_SBK.COM;1... SLS_CONVERT: All specified files have been processed. SLS_CONVERT: Cleanup being performed... B.2.4.3.4 Evaluating the ABS DCL Command Procedures – After executing the conversion utility, you can view one ABS DCL command procedure created for each SBK file that was converted, in the ABS$SLS_CONVERSION directory. The output command procedure contains: • A block of comments indicating that the file was produced by the conversion utility and the date, and time of the conversion. • Name of the SBK file represented in the command file. • The list of SBK parameters that are not converted by the conversion utility and the reason for the same. • An ABS CREATE STORAGE command to create a Storage Class (Archive). It corresponds to the MDMS Create Archive command. • An ABS CREATE ENVIRONMENT command to create an Execution Environment. • One or more ABS Save commands and ABS SET SAVE commands to create one or more Save requests. B–34 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 • The creation of a Prologue command file. The Prologue command file must be integrated with any of the site specific prologue command files to complete the functions defined by the SBK. • The creation of an Epilogue command file. The Epilogue command file must be integrated with any of the site specific epilogue command files to complete the functions defined by the SBK. The conversion utility attempts to duplicate the backup policy reflected in each SBK file. Though the command procedures can be executed immediately, it is highly recommended that you review the individual file’s contents before executing them. It is to ensure that there are no errors and the ABS Policy objects to be created accurately reflect the intended backup policy. Sample ABS DCL Command Procedure – $ EDIT ABS$ROOT:[SLS_CONVERSION]Example_ABS.COM $ !-------------------------------------------------------- $ ! SLS SBK files represented here: $ ! SLS_ABS_Example_SBK $ !$ ! SBK Symbols not yet converted: $ ! REPLY_MSG - please add to PROLOG and EPILOG $ !-------------------------------------------------------- $ ! Unsupported SBK Symbols: $ ! NEXT_JOB - use POLYCENTER Schedule Dependencies $ ! SUMMARY_FILE - use the ABS REPORT SAVE/FULL $ ! MNTFLAGS - ABS controls the way tapes are mounted $ ! SAVESET_GEN - ABS controls the name of savesets $ ! DENSITY - This is unsupported in ABS $ ! REEL_SIZE - This is unsupported in ABS $ ! QUICKLOAD - Set this parameter in TAPESTART.COM $ ! PREALLOC - This is unsupported in ABS $ ! AUTOSEL - ABS always auto-selects new tapes $ ! CONTLOADOPT - ABS requires all tapes to be labelled $ ! UNATTENDED_BACKUPS - ABS always executes unattended $ ! SBUPDT_Q - ABS Catalog updates are done in a detached process $ ! PROGRESS - This is unsupported in ABS $ ! LOG_FILE - ABS controls the name of the log file $ ! LISTING_GEN - ABS controls the name of the listing file $ ! PRINT_Q - ABS will not print the listing file Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–35
- 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: 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: 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 and 250: Migrating from SLS/MDMS V2.X to ABS
- 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 />
B.2.4.3.3 Command Syntax –<br />
$ @ABS$SYSTEM:SLS_CONVERT [] […]<br />
<br />
This parameter identifies the set of SBK files <strong>to</strong> be converted by this command. The string given<br />
must not include SLS$SYSBAK: or the _SBK.COM suffix. For example, if you want <strong>to</strong> convert<br />
the SBK file “SLS$SYSBAK:Example*_SBK.COM”, you must issue the command:<br />
$ @ABS$SYSTEM:SLS_CONVERT Example*<br />
… <br />
These optional parameters allow you <strong>to</strong> search the SBK files defined by the<br />
and only process those files that contain all the given strings. Since the<br />
SLS_CONVERT command procedure uses a /MATCH=AND on the Search command, the<br />
strings must all appear on the same line in the SBK file.<br />
Sample Conversion –<br />
$ @ABS$SYSTEM:SLS_CONVERT *<br />
Building list of SBK's from SLS$SYSBAK:*_SBK.COM;0<br />
Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example1_SBK.COM;1...<br />
Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example2_SBK.COM;1...<br />
Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example3_SBK.COM;1...<br />
Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example4_SBK.COM;1...<br />
Processing SLS$ROOT:[SYSBAK]SLS_ABS_Example5_SBK.COM;1...<br />
SLS_CONVERT: All specified files have been processed.<br />
SLS_CONVERT: Cleanup being per<strong>for</strong>med...<br />
B.2.4.3.4 Evaluating the ABS DCL Command Procedures –<br />
After executing the conversion utility, you can view one ABS DCL command procedure created<br />
<strong>for</strong> each SBK file that was converted, in the ABS$SLS_CONVERSION direc<strong>to</strong>ry. The output<br />
command procedure contains:<br />
• A block of comments indicating that the file was produced by the conversion utility and the<br />
date, and time of the conversion.<br />
• Name of the SBK file represented in the command file.<br />
• The list of SBK parameters that are not converted by the conversion utility and the reason<br />
<strong>for</strong> the same.<br />
• An ABS CREATE STORAGE command <strong>to</strong> create a S<strong>to</strong>rage Class (<strong>Archive</strong>). It corresponds<br />
<strong>to</strong> the MDMS Create <strong>Archive</strong> command.<br />
• An ABS CREATE ENVIRONMENT command <strong>to</strong> create an Execution Environment.<br />
• One or more ABS Save commands and ABS SET SAVE commands <strong>to</strong> create one or more<br />
Save requests.<br />
B–34 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X