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

4 Media Management This chapter expands on the MDMS object summary given in Chapter 2, and describes all the MDMS objects in detail, including the object attributes and operations that can be performed on the objects. Before going into details on each object, however, the use of the MDMS$CONFIGURE.COM procedure is recommended to configure your MDMS domain and the objects in it. In many cases this should take care of your entire initial configuration. 4.1 MDMS Domain Configuration 4.2 Domain If you are configuring your MDMS domain (including all objects in the domain) for the first time, HP recommends that you use the MDMS$CONFIGURE.COM command procedure. This procedure prompts you for most MDMS objects, including domain, drives, jukeboxes, media types, locations and volumes, and establishes relationships between the objects. The goal is to allow complete configuration of simple to moderately complex sites without having to read the manual. The configuration procedure offers extensive help, and contains much of the information contained in this chapter. Help is offered in a tutorial form if you answer “No” to “Have you used this procedure before”. In addition, for each question asked, you can enter “?” to have help on that question displayed. Furthermore, if you type “??” to a question, not only will the help be displayed, but in most cases a list of possible options is also displayed. This procedure is also useful when adding additional resources to an existing MDMS configuration. To invoke this procedure, enter: @MDMS$SYSTEM:MDMS$CONFIGURE.COM and just follow the questions and help. A complete example of running the procedure is shown in Appendix A. The MDMS domain encompasses all objects that are served by a single MDMS database, and all users that utilize those objects. A domain can range from a single OpenVMS cluster and its backup requirements, to multi-site configurations that may share resources over a wide area network or through Fibre Channel connections. An OpenVMS system running MDMS is considered a node within the MDMS domain, and MDMS server processes within a domain can communicate with one another. The MDMS domain object is created at initial installation, and cannot be deleted. Its main focus is to maintain domain-wide attributes and defaults, and these attributes are described in the following sections. Media Management 4–1

4<br />

Media Management<br />

This chapter expands on the MDMS object summary given in Chapter 2, and describes all the<br />

MDMS objects in detail, including the object attributes and operations that can be per<strong>for</strong>med on<br />

the objects.<br />

Be<strong>for</strong>e going in<strong>to</strong> details on each object, however, the use of the MDMS$CONFIGURE.COM<br />

procedure is recommended <strong>to</strong> configure your MDMS domain and the objects in it. In many cases<br />

this should take care of your entire initial configuration.<br />

4.1 MDMS Domain Configuration<br />

4.2 Domain<br />

If you are configuring your MDMS domain (including all objects in the domain) <strong>for</strong> the first<br />

time, <strong>HP</strong> recommends that you use the MDMS$CONFIGURE.COM command procedure. This<br />

procedure prompts you <strong>for</strong> most MDMS objects, including domain, drives, jukeboxes, media<br />

types, locations and volumes, and establishes relationships between the objects. The goal is <strong>to</strong><br />

allow complete configuration of simple <strong>to</strong> moderately complex sites without having <strong>to</strong> read the<br />

manual.<br />

The configuration procedure offers extensive help, and contains much of the in<strong>for</strong>mation contained<br />

in this chapter. Help is offered in a tu<strong>to</strong>rial <strong>for</strong>m if you answer “No” <strong>to</strong> “Have you used<br />

this procedure be<strong>for</strong>e”. In addition, <strong>for</strong> each question asked, you can enter “?” <strong>to</strong> have help on<br />

that question displayed. Furthermore, if you type “??” <strong>to</strong> a question, not only will the help be displayed,<br />

but in most cases a list of possible options is also displayed.<br />

This procedure is also useful when adding additional resources <strong>to</strong> an existing MDMS configuration.<br />

To invoke this procedure, enter:<br />

@MDMS$SYSTEM:MDMS$CONFIGURE.COM<br />

and just follow the questions and help.<br />

A complete example of running the procedure is shown in Appendix A.<br />

The MDMS domain encompasses all objects that are served by a single MDMS database, and all<br />

users that utilize those objects. A domain can range from a single <strong>OpenVMS</strong> cluster and its<br />

backup requirements, <strong>to</strong> multi-site configurations that may share resources over a wide area network<br />

or through Fibre Channel connections. An <strong>OpenVMS</strong> system running MDMS is considered<br />

a node within the MDMS domain, and MDMS server processes within a domain can<br />

communicate with one another.<br />

The MDMS domain object is created at initial installation, and cannot be deleted. Its main focus<br />

is <strong>to</strong> maintain domain-wide attributes and defaults, and these attributes are described in the following<br />

sections.<br />

Media Management 4–1

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

Saved successfully!

Ooh no, something went wrong!