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
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
- Page 17 and 18: Preface Intended Audience This docu
- Page 19 and 20: 1 Introduction The Archive Backup S
- Page 21 and 22: 2 Overview This chapter provides an
- 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 71 and 72: 4.2.7 Maximum Scratch Time 4.2.8 Me
- Page 73 and 74: 4.2.20 User Rights 4.3 Drives 4.3.1
- Page 75 and 76: 4.3.13 State Media Management 4.3 D
- Page 77 and 78: 4.4 Groups 4.4.1 Nodes 4.5 Jukeboxe
- Page 79 and 80: Media Management 4.5 Jukeboxes 4.5.
- Page 81 and 82: 4.6 Locations Media Management 4.6
- Page 83 and 84: 4.7.3 Slot Count 4.7.4 Spaces 4.7.5
- Page 85 and 86: 4.9.2 Disabled 4.9.3 OPCOM Class Me
- Page 87 and 88: Media Management 4.11 Volumes Figur
- Page 89 and 90: 4.11.2 Allocation and Movement Date
- Page 91 and 92: 4.11.5 Media Types 4.11.6 Pool Medi
- Page 93 and 94: Media Management 4.11 Volumes When
- Page 95 and 96: Media Management 4.11 Volumes When
- Page 97: 4.11.20Initialize Volume(s) Media M
- Page 100 and 101: Security 5.1 MDMS Rights 5.1 MDMS R
- Page 102 and 103: Security 5.2 Access Control 5.2 Acc
- Page 104 and 105: Security 5.3 Implementing a Securit
- Page 106 and 107: User Interfaces 6.1 Graphical User
- Page 108 and 109: User Interfaces 6.1 Graphical User
- Page 110 and 111: User Interfaces 6.1 Graphical User
- Page 112 and 113: User Interfaces 6.1 Graphical User
- Page 114 and 115: User Interfaces 6.1 Graphical User
- Page 116 and 117: User Interfaces 6.1 Graphical User
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