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.1.2
Restrictions
• Use of new functionality presented in the ABS/MDMS application that includes Oracle,
Windows, and Unix Backups
• Stronger scheduling options
• Support for new devices introduced by HP.
Refer to http://h71000.www7.hp.com/openvms/storage/smstape_matrix.html for the list of
supported devices.
ABS, an object and policy driven application uses MDMS V4.x for automatically converting the
SLS volume, slot and magazine databases, and the TAPESTART.COM command definitions to
MDMS database. It enables conversion to ABS in stages on different nodes over time, which is
called Rolling Upgrade.
SLS V2.x uses TAPESTART.COM, volume and magazine databases, various data files, and
SBK (System Backup) files to do backups. In order to use ABS/MDMS V4.x, you can choose to
do one of the following:
• Convert SLS media information to MDMS database and SLS SBK files to ABS/MDMS
objects. Then, use SLS as a client to restore data that was backed up in SLS environment.
• Transfer SLS data completely into ABS/MDMS V4.x environment and use ABS/MDMS to
do the backup and restore operations from the beginning. In this case, you will not be
migrating from SLS to ABS/MDMS.
• Migrate from SLS to ABS/MDMS; use ABS/MDMS to take further backups of the existing
SLS data and to take further fresh backups.
The conversion is comprised of the following phases:
1. SLS to MDMS conversion: This phase involves the conversion of SLS TAPESTART.COM,
volume and magazine databases into ABS/MDMS V4.x objects. The command procedure
used is 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.
2. Prev3 Support: This phase involves applying the Prev3 Support (setting the Prev3 Support
logical to “TRUE”) to use SLS as the client for viewing and restoring SLS backed up data.
See Appendix C, “Prev3 Support” for more information.
3. SLS to ABS conversion: This phase involves the conversion of SLS SBK files into ABS
V4.x objects. The command procedure used is ABS$SYSTEM:SLS_CONVERT.COM. See
Section B.2.4.3, “Converting SLS SBK Symbols to ABS Policy Objects” for more information.
• After migrating from SLS/MDMS to ABS/MDMS environment, MDMS of ABS/MDMS
does not use the existing volumes when taking further backups of existing SLS/MDMS data
or when taking fresh backups. This is because even after migration SLS/MDMS still owns
the volumes. Use fresh volumes to take further backups of existing SLS/MDMS data or to
perform fresh backups.
• After migrating from SLS/MDMS to ABS/MDMS environment, ABS/MDMS does not
allow you to restore SLS/MDMS data automatically from the SLS catalog. You need to set
the Prev3 support attribute in ABS/MDMS SYS$MANAGER:MDMS$SYSTARTUP.COM
for ABS/MDMS to take over as the server and SLS to become the client. See Appendix C,
“Prev3 Support” for more information.
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–3