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
Media Management 4.3 Drives 4.3.5 Drive Number 4.3.6 Groups 4.3.7 Jukebox 4.3.8 Media Types 4.3.9 Nodes If the drive is in a robotically-controlled jukebox, and the jukebox is controlled by MRD, you must set the drive number to the relative drive number in the jukebox used by MRD. Drives in jukeboxes are numbered from 0 to n, according to the SCSI addresses of the drives. Refer to the jukebox documentation on how to specify the relative drive number. The groups attribute contains a list of groups containing nodes that have direct access to the drive. Direct access includes direct-SCSI access, access via a controller such as an HSJ70, access via TMSCP, and access via Fibre Channel. You can specify as many groups as you wish, in addition to nodes that may not be in a group. If the drive is in a jukebox, you must specify which jukebox using the jukebox attribute. Enter a valid jukebox name from an MDMS-defined jukebox. If there is no jukebox, MDMS treats the drive as a standalone drive or as a stacker. A drive must support one or more media types in order for volumes to be used on the drive. In the media type attribute, specify one or more MDMS-defined media types that this drive can both read and write. If you wish, you can restrict the media types to a subset that you wish this drive to handle, and not all the media types it could physically handle. In this way, you can restrict the drive’s usage somewhat. The nodes attribute contains a list of nodes that have direct access to the drive. Direct access includes direct-SCSI access, access via a controller such as an HSJ70, access via TMSCP, and access via Fibre Channel. You can specify as many nodes as you wish, in addition to groups of nodes in the groups attribute. 4.3.10 Read-Only Media Types 4.3.11 Shared 4.3.12 Stacker In addition to media types that a drive can read and write, a drive may support one or more additional media types that it can only read. In the read-only media type attribute, specify one or more MDMS-defined media types that this drive can only read. This allows this drive to be used when the application operation is read-only (for example, HSM unshelves or ABS restores). Do not duplicate a media type in both the media type list and read-only media type list. You can designate whether a drive is to be used by MDMS applications and users only, or by non-MDMS users. If the drive is not shared, the MDMS server process allocates the drive on all clusters to prevent non-MDMS users and applications from allocating it. However, when an MDMS user attempts to allocate the drive, MDMS will deallocate it and allow the allocation. Set the shared attribute if you wish to share the drive with non-MDMS users, and clear if you wish to restrict usage to MDMS users. ABS users who do their own user backups are considered MDMS users, as are all system backups and HSM shelving/unshelving users. Certain types of drive can be configured as a stacker, which allows a limited automatic sequential loading capability of a set of volumes. Such drives may physically reside in a loader or have specialized hardware that allows stacker capabilities. If you wish the drive to support the stacker loading capability, set this attribute and make sure the jukebox attribute does not contain a jukebox name. If you wish the drive to operate as a jukebox or standalone drive, clear this attribute. 4-6 Media Management
4.3.13 State Media Management 4.3 Drives The drive state field determines the load state of the drive. The drive can be in one of four states: • Empty - There is no volume in the drive • Full - There is a volume in the drive • Loading - A volume is being loaded into the drive • Unloading - A volume is being unloaded from the drive This is a protected field that is normally handled by MDMS. Only modify this field if you know that there are no outstanding requests and the new state reflects the actual state of the drive. 4.3.14 Allocate Drive (DCL Only) You allocate a drive so that you can it for reading and writing data to a volume. If you allocate a drive, your process ID and node is stored in the MDMS database, and the drive is allocated in OpenVMS for your process. Because the MDMSView GUI does not operate in a process context, it is not possible to allocate drives from the GUI. You can either allocate a drive by name, or you can specify selection criteria to be used for MDMS to select an available drive for you and allocate it. The allocation selection criteria include: • Media Type - Select a drive with the specified media type • Location - Used with media type, select a drive in the specified location • Jukebox - Used with media type, select a drive in the specified jukebox • Group - Used with media type, select a drive that is supported by a node in the group • Node - Used with media type, select a drive that is supported by the node • Volume - Select a drive that is compatible with the specified volume (media type and placement) You can also specify the following options when allocating a drive: • Assist - A flag indicating whether you wish operator assistance if a drive cannot be allocated. Set if you wish assistance, and clear if you wish to use the retry limit and intervals to automatically retry (that is, wait for drives to become available). • Define - Use define to set a logical name for the drive. The logical name evaluates to both the MDMS Drive Name and the OpenVMS device name, and can be used in either MDMS or other DCL commands. • Retry Limit and Interval - If you wish the allocate to retry if there are no available drives, set the retry limit and interval, and specify noassist. • Preferred - If you allocated a drive for a specific volume, you can set preferred to request that the same drive that the volume was last loaded is the preferred drive. If you clear preferred, this forces MDMS to perform a round-robin allocation of the drives. • Reply - You can specify a symbol to receive an operator’s reply message. • Nowrite - You can specify that the drive only has to be compatible for read-only media types, as the desired operation will only read from the drive. Media Management 4–7
- Page 23 and 24: Overview 2.2 ABS Objects Figure 2-1
- Page 25 and 26: 2.2.6 Schedules 2.3 ABS Catalogs Ov
- Page 27 and 28: Overview 2.5 Media, Device and Mana
- Page 29 and 30: 2.8.3 Groups 2.8.4 Jukeboxes Overvi
- Page 31 and 32: 2.8.8 Nodes 2.8.9 Pools 2.8.10 Volu
- Page 33 and 34: 3 Saving and Restoring Data 3.1 Arc
- Page 35 and 36: 3.1.5 Destination 3.1.6 Drives 3.1.
- Page 37 and 38: 3.1.12 Volume Sets Saving and Resto
- Page 39 and 40: 3.2.5 Staging 3.2.6 Catalog Save En
- Page 41 and 42: • Save Type - Copied from related
- Page 43 and 44: Example 3-4 Staging Information in
- Page 45 and 46: 3.4.3 Compression 3.4.4 Data Safety
- Page 47 and 48: Saving and Restoring Data 3.4 Envir
- Page 49 and 50: Saving and Restoring Data 3.5 Saves
- Page 51 and 52: Saving and Restoring Data 3.5 Saves
- Page 53 and 54: Table 3-3 Disk, File, Path and Data
- Page 55 and 56: Saving and Restoring Data 3.5 Saves
- Page 57 and 58: Saving and Restoring Data 3.5 Saves
- Page 59 and 60: • First disk/file specification p
- Page 61 and 62: 3.5.17.1 HOLIDAYS.DAT Record Format
- Page 63 and 64: Saving and Restoring Data 3.6 Selec
- Page 65 and 66: 3.7.2 Command 3.7.3 Restriction Sav
- Page 67: 3.7.5 Include and Exclude 3.7.6 Tim
- Page 70 and 71: Media Management 4.2 Domain 4.2.1 A
- Page 72 and 73: Media Management 4.2 Domain 4.2.15
- Page 76 and 77: Media Management 4.3 Drives 4.3.15
- Page 78 and 79: Media Management 4.5 Jukeboxes 4.5.
- Page 80 and 81: Media Management 4.5 Jukeboxes 4.5.
- Page 82 and 83: Media Management 4.7 Magazines 4.6.
- Page 84 and 85: Media Management 4.8 Media Types 4.
- Page 86 and 87: Media Management 4.11 Volumes 4.10.
- Page 88 and 89: Media Management 4.11 Volumes Table
- Page 90 and 91: Media Management 4.11 Volumes 4.11.
- Page 92 and 93: Media Management 4.11 Volumes neede
- Page 94 and 95: Media Management 4.11 Volumes • R
- Page 96 and 97: Media Management 4.11 Volumes 4.11.
- Page 99 and 100: 5 Security The security model used
- Page 101 and 102: Security 5.1 MDMS Rights Table 5-1
- Page 103 and 104: Table 5-4 Domain Access Control Opt
- Page 105 and 106: 6 User Interfaces ABS and MDMS supp
- Page 107 and 108: 6.1.3 Logging In User Interfaces 6.
- Page 109 and 110: User Interfaces 6.1 Graphical User
- Page 111 and 112: User Interfaces 6.1 Graphical User
- Page 113 and 114: Figure 6-5 Domain View Showing Expa
- Page 115 and 116: User Interfaces 6.1 Graphical User
- Page 117 and 118: 6.1.13 Viewing MDMS Audit and Event
- Page 119 and 120: 6.2.1 Syntax Overview User Interfac
- Page 121 and 122: User Interfaces 6.3 User Interface
- Page 123 and 124: 7 Preparing For Disaster Recovery I
Media Management<br />
4.3 Drives<br />
4.3.5 Drive Number<br />
4.3.6 Groups<br />
4.3.7 Jukebox<br />
4.3.8 Media Types<br />
4.3.9 Nodes<br />
If the drive is in a robotically-controlled jukebox, and the jukebox is controlled by MRD, you<br />
must set the drive number <strong>to</strong> the relative drive number in the jukebox used by MRD. Drives in<br />
jukeboxes are numbered from 0 <strong>to</strong> n, according <strong>to</strong> the SCSI addresses of the drives. Refer <strong>to</strong> the<br />
jukebox documentation on how <strong>to</strong> specify the relative drive number.<br />
The groups attribute contains a list of groups containing nodes that have direct access <strong>to</strong> the<br />
drive. Direct access includes direct-SCSI access, access via a controller such as an HSJ70,<br />
access via TMSCP, and access via Fibre Channel. You can specify as many groups as you wish,<br />
in addition <strong>to</strong> nodes that may not be in a group.<br />
If the drive is in a jukebox, you must specify which jukebox using the jukebox attribute. Enter a<br />
valid jukebox name from an MDMS-defined jukebox. If there is no jukebox, MDMS treats the<br />
drive as a standalone drive or as a stacker.<br />
A drive must support one or more media types in order <strong>for</strong> volumes <strong>to</strong> be used on the drive. In<br />
the media type attribute, specify one or more MDMS-defined media types that this drive can<br />
both read and write. If you wish, you can restrict the media types <strong>to</strong> a subset that you wish this<br />
drive <strong>to</strong> handle, and not all the media types it could physically handle. In this way, you can<br />
restrict the drive’s usage somewhat.<br />
The nodes attribute contains a list of nodes that have direct access <strong>to</strong> the drive. Direct access<br />
includes direct-SCSI access, access via a controller such as an HSJ70, access via TMSCP, and<br />
access via Fibre Channel. You can specify as many nodes as you wish, in addition <strong>to</strong> groups of<br />
nodes in the groups attribute.<br />
4.3.10 Read-Only Media Types<br />
4.3.11 Shared<br />
4.3.12 Stacker<br />
In addition <strong>to</strong> media types that a drive can read and write, a drive may support one or more additional<br />
media types that it can only read. In the read-only media type attribute, specify one or<br />
more MDMS-defined media types that this drive can only read. This allows this drive <strong>to</strong> be used<br />
when the application operation is read-only (<strong>for</strong> example, HSM unshelves or ABS res<strong>to</strong>res). Do<br />
not duplicate a media type in both the media type list and read-only media type list.<br />
You can designate whether a drive is <strong>to</strong> be used by MDMS applications and users only, or by<br />
non-MDMS users. If the drive is not shared, the MDMS server process allocates the drive on all<br />
clusters <strong>to</strong> prevent non-MDMS users and applications from allocating it. However, when an<br />
MDMS user attempts <strong>to</strong> allocate the drive, MDMS will deallocate it and allow the allocation. Set<br />
the shared attribute if you wish <strong>to</strong> share the drive with non-MDMS users, and clear if you wish <strong>to</strong><br />
restrict usage <strong>to</strong> MDMS users. ABS users who do their own user backups are considered MDMS<br />
users, as are all system backups and HSM shelving/unshelving users.<br />
Certain types of drive can be configured as a stacker, which allows a limited au<strong>to</strong>matic sequential<br />
loading capability of a set of volumes. Such drives may physically reside in a loader or have<br />
specialized hardware that allows stacker capabilities. If you wish the drive <strong>to</strong> support the stacker<br />
loading capability, set this attribute and make sure the jukebox attribute does not contain a jukebox<br />
name. If you wish the drive <strong>to</strong> operate as a jukebox or standalone drive, clear this attribute.<br />
4-6 Media Management