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
D Upgrading from ABS V2.X/V3.X to V4.x Environment D.1 Introduction This appendix describes the various conversion activities that are needed when upgrading to ABS/MDMS V4.x from previous versions of ABS. These upgrades from V2.x or V3.x are described under different headings for your reference. For upgrading from ABS V2.x/V3.x to the latest version, separate procedures are provided that guide you to through the upgrade process. It also covers converting specific catalog format, RMS and RDB policy databases. D.2 Upgrading from ABS/MDMS V2.x/V3.x to V4.x This section on upgrading from ABS/MDMS V2.x/V3.x provides details on the version specific upgrade command procedures that must be executed to upgrade to an ABS/MDMS V4.x version. It also involves converting the catalog formats, RMS and RDB policy databases. D.2.1 Converting ABS/MDMS V2.x to ABS/MDMS V4.x ABS V2.x uses TAPESTART.COM, Volume and Magazine databases, and various data files for Media Management. It also uses ABS Policy database for the ABS objects. You might want to convert the media information into the MDMS databases or create new objects. In ABS/MDMS V4.x, the ABS Policy Engine has been moved into the MDMS server. To upgrade to ABS V4.x, the ABS 2.x or 3.x Policy database information must be exported to the MDMS database. You also need to do some catalog modifications. Note If you are using an ABS RDB policy database, it must be converted to an RMS database before exporting the data to the V4.x format. The RDB conversion must be done before updating to V4.x. See Section D.2.5, “Converting ABS V2.x/V3.x RDB Policy Database to ABS V4.x (MDMS Server Database)”. • To convert TAPESTART.COM, Volume and Magazine databases into ABS/MDMS V4.x databases, use the command procedure MDMS$SYSTEM: MDMS$CONVERT_V2_TO_V3. See Section D.2.2, “Converting ABS V3.0B and MDMS 2.x to ABS/MDMS V4.x” for more information. • To convert ABS catalogs, use SYS$SYSTEM:ABS$CATALOG_UPGRADE.EXE. See Section D.2.4, “Converting ABS V2.x Catalogs to V4.x Format” for more information. • To convert the ABS RDB database to an RMS database, see Section D.2.5, “Converting ABS V2.x/V3.x RDB Policy Database to ABS V4.x (MDMS Server Database)” for more information. Upgrading from ABS V2.X/V3.X to V4.x Environment D–1
- 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 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 265 and 266: Upgrading from ABS V2.X/V3.X to V4.
- Page 267 and 268: E ABS/MDMS Support for Fibre Channe
- Page 269 and 270: Comment: E.4 Multipathing ABS/MDMS
- Page 271: Guidelines for OpenVMSCluster Confi
- Page 274 and 275: Date Specifications 3-32 Date Type
- Page 276 and 277: RETAIN VERSION 3-29 Retention Days
D<br />
Upgrading from ABS V2.X/V3.X <strong>to</strong> V4.x<br />
Environment<br />
D.1 Introduction<br />
This appendix describes the various conversion activities that are needed when upgrading <strong>to</strong><br />
ABS/MDMS V4.x from previous versions of ABS. These upgrades from V2.x or V3.x are<br />
described under different headings <strong>for</strong> your reference.<br />
For upgrading from ABS V2.x/V3.x <strong>to</strong> the latest version, separate procedures are provided that<br />
guide you <strong>to</strong> through the upgrade process. It also covers converting specific catalog <strong>for</strong>mat,<br />
RMS and RDB policy databases.<br />
D.2 Upgrading from ABS/MDMS V2.x/V3.x <strong>to</strong> V4.x<br />
This section on upgrading from ABS/MDMS V2.x/V3.x provides details on the version specific<br />
upgrade command procedures that must be executed <strong>to</strong> upgrade <strong>to</strong> an ABS/MDMS V4.x version.<br />
It also involves converting the catalog <strong>for</strong>mats, RMS and RDB policy databases.<br />
D.2.1 Converting ABS/MDMS V2.x <strong>to</strong> ABS/MDMS V4.x<br />
ABS V2.x uses TAPESTART.COM, Volume and Magazine databases, and various data files <strong>for</strong><br />
Media Management. It also uses ABS Policy database <strong>for</strong> the ABS objects. You might want <strong>to</strong><br />
convert the media in<strong>for</strong>mation in<strong>to</strong> the MDMS databases or create new objects. In ABS/MDMS<br />
V4.x, the ABS Policy Engine has been moved in<strong>to</strong> the MDMS server. To upgrade <strong>to</strong> ABS V4.x,<br />
the ABS 2.x or 3.x Policy database in<strong>for</strong>mation must be exported <strong>to</strong> the MDMS database. You<br />
also need <strong>to</strong> do some catalog modifications.<br />
Note<br />
If you are using an ABS RDB policy database, it must be converted <strong>to</strong> an RMS database<br />
be<strong>for</strong>e exporting the data <strong>to</strong> the V4.x <strong>for</strong>mat. The RDB conversion must be done<br />
be<strong>for</strong>e updating <strong>to</strong> V4.x. See Section D.2.5, “Converting ABS V2.x/V3.x RDB Policy<br />
Database <strong>to</strong> ABS V4.x (MDMS Server Database)”.<br />
• To convert TAPESTART.COM, Volume and Magazine databases in<strong>to</strong> ABS/MDMS V4.x<br />
databases, use the command procedure MDMS$SYSTEM:<br />
MDMS$CONVERT_V2_TO_V3. See Section D.2.2, “Converting ABS V3.0B and MDMS<br />
2.x <strong>to</strong> ABS/MDMS V4.x” <strong>for</strong> more in<strong>for</strong>mation.<br />
• To convert ABS catalogs, use SYS$SYSTEM:ABS$CATALOG_UPGRADE.EXE. See<br />
Section D.2.4, “Converting ABS V2.x Catalogs <strong>to</strong> V4.x Format” <strong>for</strong> more in<strong>for</strong>mation.<br />
• To convert the ABS RDB database <strong>to</strong> an RMS database, see Section D.2.5, “Converting<br />
ABS V2.x/V3.x RDB Policy Database <strong>to</strong> ABS V4.x (MDMS Server Database)” <strong>for</strong> more<br />
in<strong>for</strong>mation.<br />
Upgrading from ABS V2.X/V3.X <strong>to</strong> V4.x Environment D–1