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
Upgrading from ABS V2.X/V3.X to V4.x Environment D.2 Upgrading from ABS/MDMS V2.x/V3.x to V4.x • To convert the ABS Policy database to V4.x format, use SYS$SYSTEM: ABS$CONVERT_V3_TO_V4.EXE. See Section D.2.6, “Converting ABS V3.x RMS Policy Database to ABS V4.x (MDMS Server Database)” for more information. D.2.2 Converting ABS V3.0B and MDMS 2.x to ABS/MDMS V4.x MDMS V2.x uses TAPESTART.COM, Volume and Magazine databases. You might want to convert them into the MDMS databases or create new objects. ABS V3.0B uses the ABS policy databases which must be moved to the MDMS database. • To convert TAPESTART.COM, Volume and Magazine databases into MDMS V4.x, use the command procedure MDMS$SYSTEM: MDMS$CONVERT_V2_TO_V4. See Section B.2.4.1, “Converting SLS/MDMS V2.x Symbols and Database Files to ABS/MDMS V4.x” for more information. • To convert the ABS policy database into the V4.x format, use ABS$SYSTEM: ABS$CONVERT_V3_TO_V4.EXE. See Section D.2.6, “Converting ABS V3.x RMS Policy Database to ABS V4.x (MDMS Server Database)” for more information. D.2.3 Converting ABS/MDMS V3.1x or 3.2x to ABS/MDMS V4.x MDMS V3.x needs no conversion to work with ABS/MDMS V4.x. ABS V3.1 or V3.2 uses the ABS policy database that must be moved into the MDMS database. • To convert the ABS Policy database to V4.x format, use ABS$SYSTEM: ABS$CONVERT_V3_TO_V4.EXE. D.2.4 Converting ABS V2.x Catalogs to V4.x Format If you are upgrading from ABS V2.1, 2.1A or 2.1B, you must convert the catalog format before using them in ABS V4.x. The catalog upgrade utility upgrades catalogs from their previous formats to the new V4.x formats and also deletes expired summary records from those catalogs. The log file ABS_LOG:ABS_CATALOG_V22_UPGRADE.LOG is generated with information about all of the catalog entries that are modified or deleted. The catalog upgrade has an update parameter called “p1” that requires the name of the catalog you want to upgrade, as the input. You can use the catalog upgrade to upgrade a single ABS catalog or all the ABS catalogs. To upgrade a single ABS catalog, specify the catalog name as to the input to the “p1” parameter. To upgrade all the catalogs, enter an asterisk “*” as the wildcard character or leave the “p1” parameter blank. Follow these steps to execute the utility: 1. Define the following symbol: $ CATALOG_UPGRADE :== $ABS_SYSTEM:ABS$CATALOG_UPGRADE.EXE 2. Enter one of the following commands: $ CATALOG_UPGRADE ! upgrades all ABS catalogs $ CATALOG_UPGRADE * !equivalent to example above $ CATALOG_UPGRADE ABS_CATALOG ! Upgrades a catalog named ABS_CATALOG D–2 Upgrading from ABS V2.X/V3.X to V4.x Environment
Upgrading from ABS V2.X/V3.X to V4.x Environment D.2 Upgrading from ABS/MDMS V2.x/V3.x to V4.x Note The ABS cagtalogs must be inactive while the catalog upgrade utility is executed. The catalog that is being upgraded will be locked; no save, restore, or lookup operations are allowed while the upgrade is in progress. D.2.5 Converting ABS V2.x/V3.x RDB Policy Database to ABS V4.x (MDMS Server Database) If you are still using an RDB Policy database, the command procedure to convert it to RMS is available in the previous versions of ABS. You need to extract the command procedure from one of the earlier ABS kits or contact HP Customer Support for assistance. Note The ABS V2.x/V3.x RDB Policy database conversion must be done prior to updating to V4.x. Follow these steps to convert ABS V2.x or 3.x RDB Policy database to V4.x. 1. Before updating to V4.x, convert the RDB Policy database to RMS Policy database using the conversion programs provided with the ABS V3.1A or V3.2 kits. $ @ ABS$SYSTEM:ABS$CONVERT_TO_RMS 2. Convert the RMS Policy database to MDMS database as described in Section D.2.6, “Converting ABS V3.x RMS Policy Database to ABS V4.x (MDMS Server Database)” for more information. D.2.6 Converting ABS V3.x RMS Policy Database to ABS V4.x (MDMS Server Database) Pre-requisites Before upgrading to V4.x, type “ABS SHOW /FULL. This command provides the required objects’ details in an output file, which you can use for reference after the upgrade. Then upgrade to V4.x and execute the following steps to convert the ABS policy database to V4.x: Before executing the conversion, ensure that the following are verified: • The old ABS Policy database files (ABS$DATABASE:EPCOT.DB%) are not being used at present. • ABS V4.x and MDMS V4.x are configured and running on all the Clients and Servers. Run the SYS$SYSTEM: ABS$CONVERT_V3_TO_V4.EXE utility to convert the ABS 3.x database to MDMS Database. The utility exports only the highest version of the Policy object. Details of new MDMS objects created are logged in ABS$CONVERT_V3_TO_V4.LOG. Upgrading from ABS V2.X/V3.X to V4.x Environment D–3
- 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 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 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
Upgrading from ABS V2.X/V3.X <strong>to</strong> V4.x Environment<br />
D.2 Upgrading from ABS/MDMS V2.x/V3.x <strong>to</strong> V4.x<br />
• To convert the ABS Policy database <strong>to</strong> V4.x <strong>for</strong>mat, use SYS$SYSTEM:<br />
ABS$CONVERT_V3_TO_V4.EXE. See Section D.2.6, “Converting ABS V3.x RMS Policy<br />
Database <strong>to</strong> ABS V4.x (MDMS Server Database)” <strong>for</strong> more in<strong>for</strong>mation.<br />
D.2.2 Converting ABS V3.0B and MDMS 2.x <strong>to</strong> ABS/MDMS V4.x<br />
MDMS V2.x uses TAPESTART.COM, Volume and Magazine databases. You might want <strong>to</strong> convert<br />
them in<strong>to</strong> the MDMS databases or create new objects. ABS V3.0B uses the ABS policy<br />
databases which must be moved <strong>to</strong> the MDMS database.<br />
• To convert TAPESTART.COM, Volume and Magazine databases in<strong>to</strong> MDMS V4.x, use the<br />
command procedure MDMS$SYSTEM: MDMS$CONVERT_V2_TO_V4. See Section<br />
B.2.4.1, “Converting SLS/MDMS V2.x Symbols and Database Files <strong>to</strong> ABS/MDMS V4.x”<br />
<strong>for</strong> more in<strong>for</strong>mation.<br />
• To convert the ABS policy database in<strong>to</strong> the V4.x <strong>for</strong>mat, use ABS$SYSTEM:<br />
ABS$CONVERT_V3_TO_V4.EXE. See Section D.2.6, “Converting ABS V3.x RMS Policy<br />
Database <strong>to</strong> ABS V4.x (MDMS Server Database)” <strong>for</strong> more in<strong>for</strong>mation.<br />
D.2.3 Converting ABS/MDMS V3.1x or 3.2x <strong>to</strong> ABS/MDMS V4.x<br />
MDMS V3.x needs no conversion <strong>to</strong> work with ABS/MDMS V4.x. ABS V3.1 or V3.2 uses the<br />
ABS policy database that must be moved in<strong>to</strong> the MDMS database.<br />
• To convert the ABS Policy database <strong>to</strong> V4.x <strong>for</strong>mat, use ABS$SYSTEM:<br />
ABS$CONVERT_V3_TO_V4.EXE.<br />
D.2.4 Converting ABS V2.x Catalogs <strong>to</strong> V4.x Format<br />
If you are upgrading from ABS V2.1, 2.1A or 2.1B, you must convert the catalog <strong>for</strong>mat be<strong>for</strong>e<br />
using them in ABS V4.x. The catalog upgrade utility upgrades catalogs from their previous <strong>for</strong>mats<br />
<strong>to</strong> the new V4.x <strong>for</strong>mats and also deletes expired summary records from those catalogs.<br />
The log file ABS_LOG:ABS_CATALOG_V22_UPGRADE.LOG is generated with in<strong>for</strong>mation<br />
about all of the catalog entries that are modified or deleted.<br />
The catalog upgrade has an update parameter called “p1” that requires the name of the catalog<br />
you want <strong>to</strong> upgrade, as the input.<br />
You can use the catalog upgrade <strong>to</strong> upgrade a single ABS catalog or all the ABS catalogs. To<br />
upgrade a single ABS catalog, specify the catalog name as <strong>to</strong> the input <strong>to</strong> the “p1” parameter. To<br />
upgrade all the catalogs, enter an asterisk “*” as the wildcard character or leave the “p1” parameter<br />
blank.<br />
Follow these steps <strong>to</strong> execute the utility:<br />
1. Define the following symbol:<br />
$ CATALOG_UPGRADE :== $ABS_SYSTEM:ABS$CATALOG_UPGRADE.EXE<br />
2. Enter one of the following commands:<br />
$ CATALOG_UPGRADE ! upgrades all ABS catalogs<br />
$ CATALOG_UPGRADE * !equivalent <strong>to</strong> example above<br />
$ CATALOG_UPGRADE ABS_CATALOG ! Upgrades a catalog named ABS_CATALOG<br />
D–2 Upgrading from ABS V2.X/V3.X <strong>to</strong> V4.x Environment