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
• Physically inserting volumes into a jukebox and then issuing the INVENTORY JUKE-
BOX/CREATE command that references a jukebox/slot range (MRD only), or a volume
range (DCSC only). Volume attributes can be set from an inherited volume or a media type
can be specified. You can later use the SET VOLUME to customize other attributes.
• Using the LOAD DRIVE/CREATE command to perform scratch loads in non-jukebox
drives. Volume attributes can be set from an inherited volume or the media type can be specified.
You can later use the SET VOLUME command to customize other attributes.
Once a volume is created and initial attributes are set, it is not normally necessary to use the SET
VOLUME command to change the attributes. Rather, the attributes are automatically modified
when certain commands like the ALLOCATE VOLUME or the LOAD VOLUME commands
are issued. However, in some cases, the volume database and physical reality may get out of synchronization.
In such cases, you can use the SET VOLUME command to correct the database.
Note that several fields in the volume object are designated as "PROTECTED". MDMS uses
these fields to control the volume's operations within its environment. You need special privileges
to modify the protected fields; in the GUI you need to select the "Enable Protected" (displayed
in the pop up menu when you right-click on the screen) to make these fields writable.
When changing a protected field, you must ensure that its new value is consistent with other
attributes. For example, if you are manually setting the volume's placement to jukebox, you must
first ensure that a jukebox name is defined.
Two key attributes in the volume object are "State” and "Placement". Following are the volume
states:
• Uninitialized: Default state for a volume that is just then created. A volume cannot be allocated
in this state. You must either initialize the volume using the MDMS INITIALIZE
command or set the volume to the “Free” state using the MDMS SET VOLUME/PREINI-
TIALIZED command.
• Free: Equivalent to the MDMS V2 “Free” state, a volume can be initialized in this state
• Allocated: Equivalent to the MDMS V2 “Allocated” state. An Allocated volume cannot be
deleted or re-used unless it is released.
• Transition: Equivalent to the MDMS V2 “Transition” state that forbids re-allocation for
some time called the Transition Time. Deallocating or releasing a volume will either place it
in the “Transition” state or the “Free” state, depending on the Transition time.
• Unavailable: Equivalent to the MDMS V2 “Down” state that removes a volume from use
The “PLACEMENT” attribute is a new attribute in MDMS V3. It describes a volume's current
placement. The volume can be placed in a drive, jukebox, magazine or onsite/offsite location.
The placement can also be "MOVING", which means that the volume is changing placements
but the change is not yet complete. Volume Load, Unload or Move commands cannot be issued
to a volume whose placement is shown as “Moving”. While a volume is moving, it is sometimes
necessary for an operator to determine its destination.
Example: When a volume is moved from a jukebox to an onsite location and space, the operator
can issue the SHOW VOLUME command for moving volumes to specific locations. The command
provides the exact destination/location where the volume is supposed to be moved.
The new MDMS V3 CREATE VOLUME command replaces the previous Storage "ADD VOL-
UME" command. For maintaining consistency, most attributes are supported for both the CRE-
ATE VOLUME and SET VOLUME commands.
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–17