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.9 Disabling the SLS SBK Files –
It is very important to note that once you have executed the DCL Command procedures, the
ABS Save requests will be executing according to their schedules. It means that you will be performing
both SLS and ABS backups if you do not disable the SLS SBK files.
The SLS SBK files can be disabled by leaving their DAYS_n and TIME_n qualifiers blank or by
commenting out these qualifiers. This causes SLS to no longer schedule the SBK files for execution.
Since SLS and ABS use different media management subsystems, it is highly recommended that
you do not use both products on the same node. If you do, you will find that the SLS and MDMS
volume databases can become unsynchronized. There can also be contention and other unexpected
troubles with drives and jukeboxes. If you want to stage your SLS to ABS conversion
across the network, the following approach is recommended:
• Define your database server as your first set of nodes to convert; these nodes will execute
the MDMS database server.
• Perform the MDMS conversion on these nodes (see Section B.2.4.1, “Converting
SLS/MDMS V2.x Symbols and Database Files to ABS/MDMS V4.x”).
• Perform the ABS conversion on these nodes (see Section B.2.4.3, “Converting SLS SBK
Symbols to ABS Policy Objects”).
• On other client nodes still running SLS, define the symbol DB_NODES in the TAPE-
START.COM to point to nodes in the ABS/MDMS database server.
After the conversion on the server node, MDMS V4.x will start managing the volume, magazine
and slot databases but the client systems are still able to use SLS as the backup paradigm. It is
recommended that you convert the remainder of your systems to ABS/MDMS V4.x as early as
possible, because some of the more unusual features of SLS/MDMS V2.x are not supported by
the new ABS/MDMS V4.x database server.
B.2.4.3.10 Converting User Backup policy –
The conversion utility does not convert User Backup policy automatically. It is only intended to
make converting SBK files easier or automatic.
Note
There is no automatic way to set up archives for the entire user population or for a
large set of users. The only way to accomplish the task is by creating a DCL command
procedure and issuing the correct ABS DCL commands.
B.2.4.3.11 Monitoring ABS Activity –
After implementing your backup policy in ABS, you should carefully monitor the activities of
ABS until you are confident that your policy is being executed as intended. There are three ways
to monitor ABS activity:
• View the schedules (MDMS SHOW SCHEDULE or MDMS SHOW SAVE *).
• Set up Notification criteria on the Environments to send you e-mail when ABS operations
complete. The e-mail will contain the name of the job and the final status.
• Examine the ABS Log files. All ABS Log files are created in the ABS$LOG: directory and
are given the same name as the Save request.
• For catalog operations, you can do the following:
B–48 Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X