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

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

Overview 2.8 MDMS Objects 2.8.5 Locations 2.8.6 Magazines 2.8.7 Media Types • The threshold value for free volumes in the jukebox (before a warning is issued) • The groups and nodes that have direct access to the jukebox, including access via Fibre Channel • The state of the jukebox A location describes the physical location of other objects, and is used as a selection criterion for allocating drives and volumes, and for placing tape volumes in a specific place. Locations can exist in a hierarchy, and as such are considered compatible locations for allocation purposes if locations share a common root in the hierarchy. Locations only have two attributes: • Parent location - The parent location in the hierarchy (a location need not have a parent location) • Spaces - A range of “spaces” to be used for storing volumes, also optional. A magazine is a logical object that contains a set of volumes that are to be moved as a group. Magazines typically relate to a physical magazine that certain jukeboxes require in order to move volumes in and out of a jukebox (for example, a TZ877 or TLZ9L). However, even for jukeboxes requiring physical magazines, it is not a requirement to configure MDMS magazines if you want to treat the movement of the individual volumes independently. Magazines contain the following attributes: • Slot count • Placement • Jukebox name, start slot or position • Onsite and offsite locations and dates When a volume is in a magazine, its placement and associated locations are those of the magazine. Magazines can be scheduled to move onsite and offsite. In most cases, this means that all the volumes in the magazine are moved onsite or offsite; the physical magazine itself usually stays with the jukebox with a new set of volumes. The use of magazines is not required. A media type is a logical object that describes certain attributes of tape volume media. Media types are used as a major selection criterion for drive and volume allocation, and are used to match volumes with compatible drives. Media types contain the following attributes: • Density - A density value or keyword that identifies the density of the media. This value must be one of the keyword values supported by OpenVMS. Density is used in initializing volumes. • Compaction - A flag indicating whether compaction is desired on volumes. Setting compaction usually results in about twice as much data capacity for a tape volume. • Capacity - The size of the media in MB (not used by MDMS). • Length - The length of the media in feet (not used by MDMS). 2-10 Overview

2.8.8 Nodes 2.8.9 Pools 2.8.10 Volumes Overview 2.9 Getting Started A node is an OpenVMS system in the MDMS domain that is running MDMS. Every node in the domain must have a node definition, which describes the network transports and other information applicable to that system. Node attributes include: • Location of the node • OPCOM classes to be used for OPCOM messages on the node • Supported network transports and transport full names A pool is a logical object that contains a set of volumes that can be allocated and used by a set of authorized users. It is one way to separate volumes belonging to different organizations and allowing only users of those organizations to use the volumes. Pool attributes include: • Authorized users - A list of users in node::username format that are authorized to allocate and use volumes in the pool • Default users - A list of users in node::username format that are not only authorized to use volumes, but that use volumes from this pool by default. • Threshold - A minimum value of free volumes in the pool, below which an OPCOM warning message is sent. A user need only be defined in one of the lists to be able to use volumes in the pool. The use of pools is not required. A volume is a single piece of tape media that MDMS applications (ABS and HSM) use to store tape-related data. Volumes contains many attributes that are used to describe the type of volume, its placement and location, and dates for scheduling allocation and movement. Volume attributes include: • Media type and pool for the volume • Placement and placement objects such as jukebox, slot, location, magazine • Onsite and offsite locations and scheduled dates • Allocation state, user and scheduled scratch date • Formatting information • Volume protection • Counters 2.9 Getting Started • Historical information dates This section provides a simple example of how to configure a minimal ABS/MDMS domain and create a save and restore request. Although most configurations are more complex than this, it serves to illustrate how to use the MDMS configuration procedure and the default objects provided by ABS. Overview 2–11

Overview<br />

2.8 MDMS Objects<br />

2.8.5 Locations<br />

2.8.6 Magazines<br />

2.8.7 Media Types<br />

• The threshold value <strong>for</strong> free volumes in the jukebox (be<strong>for</strong>e a warning is issued)<br />

• The groups and nodes that have direct access <strong>to</strong> the jukebox, including access via Fibre<br />

Channel<br />

• The state of the jukebox<br />

A location describes the physical location of other objects, and is used as a selection criterion <strong>for</strong><br />

allocating drives and volumes, and <strong>for</strong> placing tape volumes in a specific place. Locations can<br />

exist in a hierarchy, and as such are considered compatible locations <strong>for</strong> allocation purposes if<br />

locations share a common root in the hierarchy.<br />

Locations only have two attributes:<br />

• Parent location - The parent location in the hierarchy (a location need not have a parent<br />

location)<br />

• Spaces - A range of “spaces” <strong>to</strong> be used <strong>for</strong> s<strong>to</strong>ring volumes, also optional.<br />

A magazine is a logical object that contains a set of volumes that are <strong>to</strong> be moved as a group.<br />

Magazines typically relate <strong>to</strong> a physical magazine that certain jukeboxes require in order <strong>to</strong><br />

move volumes in and out of a jukebox (<strong>for</strong> example, a TZ877 or TLZ9L). However, even <strong>for</strong><br />

jukeboxes requiring physical magazines, it is not a requirement <strong>to</strong> configure MDMS magazines<br />

if you want <strong>to</strong> treat the movement of the individual volumes independently.<br />

Magazines contain the following attributes:<br />

• Slot count<br />

• Placement<br />

• Jukebox name, start slot or position<br />

• Onsite and offsite locations and dates<br />

When a volume is in a magazine, its placement and associated locations are those of the magazine.<br />

Magazines can be scheduled <strong>to</strong> move onsite and offsite. In most cases, this means that all<br />

the volumes in the magazine are moved onsite or offsite; the physical magazine itself usually<br />

stays with the jukebox with a new set of volumes.<br />

The use of magazines is not required.<br />

A media type is a logical object that describes certain attributes of tape volume media. Media<br />

types are used as a major selection criterion <strong>for</strong> drive and volume allocation, and are used <strong>to</strong><br />

match volumes with compatible drives. Media types contain the following attributes:<br />

• Density - A density value or keyword that identifies the density of the media. This value<br />

must be one of the keyword values supported by <strong>OpenVMS</strong>. Density is used in initializing<br />

volumes.<br />

• Compaction - A flag indicating whether compaction is desired on volumes. Setting compaction<br />

usually results in about twice as much data capacity <strong>for</strong> a tape volume.<br />

• Capacity - The size of the media in MB (not used by MDMS).<br />

• Length - The length of the media in feet (not used by MDMS).<br />

2-10 Overview

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!