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.9 Getting Started Before creating save or restore requests, you should first configure the media management environment. This includes the tape volumes, drives, jukeboxes and other media management objects that you may want to use. The recommended way to do this is to run the MDMS configuration command procedure, which offers an online tutorial and help in defining the configuration. During execution of this procedure, type “?” to get help on any question, and type “??” to get help and (in many cases) a list of existing objects or possible values for answers to questions. To invoke this procedure: @MDMS$SYSTEM:MDMS$CONFIGURE A complete example of running this procedure is provided in Appendix A. Having completed the media management configuration, creating a save or restore request in ABS can be very simple if you elect to use the default archives, environments and selection objects. The minimum amount of information you need to specify for a save or restore request is: • The name of the save or restore. • The disks or files to be saved. • The start time of the save. ABS tries to determine the type of data being saved based on the format of the file specification and assigns by default a relevant archive and environment. So, for example, a save request can be specified and executed in a single DCL command as follows: $ MDMS CREATE SAVE MY_SAVE/INCLUDE=DISK$USER1:[SMITH...]/START This command creates a save called MY_SAVE, includes the file specification DISK$USER1:[SMITH...] (all files), and starts the save immediately. MDMS determines that this is a save of VMS files based on the file format, and assigns archive SYSTEM_BACKUPS and environment SYSTEM_BACKUPS_ENV, and creates a default selection and schedule. With this save definition, a default frequency of ONE_TIME_ONLY is assigned, and the save is not scheduled for regular execution. A restore can also be defined. For example, to restore the same files that were saved in MY_SAVE, you can enter the following command: $ MDMS CREATE RESTORE MY_RESTORE/INCLUDE=DISK$USER1:[SMITH...]/START This command creates a restore called MY_RESTORE, includes the file specification DISK$USER1:[SMITH...] (all files), and starts the restore immediately. MDMS determines that this is a restore of VMS files based on the file format, and assigns archive SYSTEM_BACKUPS and environment SYSTEM_BACKUPS_ENV, and creates a default selection and schedule. With this restore definition, a default frequency of ONE_TIME_ONLY is assigned, and the restore is not scheduled for regular execution. Note Define the logical referring to the disk name before executing the restore request. For more information, see the note given in Section 3.5.8, “Destination (Restore Only)”. Since these requests were defined with a frequency of ONE_TIME_ONLY, ABS will automatically delete them after a default interval of 3 days after execution. Of course, creating the backup environment to backup all data in your production environment will involve more complex definitions, including creating your own archives, environments and in some cases selections and schedules. Chapter 3, Saving and Restoring Data, describes all the ABS objects in detail. 2-12 Overview

3 Saving and Restoring Data 3.1 Archives This chapter expands upon the ABS Overview in Chapter 2 and describes saving and restoring in detail by discussing the ABS objects, and the meanings, possible values and uses for all attributes. For each object, the attributes are listed in alphabetical order for easy reference, but related attributes are discussed together. The attributes are described without specific syntax or instructions on how to manipulate them, but are named according to the qualifiers in the CLI and attributes on the MDMSView GUI screens. For information on the syntax and semantic rules for each object and attribute, refer to the MDMS Reference Guide. All objects have an owner, and optional access control which limits access to the object. Since these attributes are common to all objects, they are described in Chapter 6, Security, instead of this chapter. In addition, ABS supports inheriting attributes from one object to another when creating a new object. For example, if you want to create a new save request SAVE2, but use most of the attributes from another save request SAVE1, you can specify SAVE1 as the inherit attribute when you create SAVE2. From there you can modify SAVE2 to define its unique characteristics. This philosophy applies to all ABS and MDMS objects. You can even inherit restore requests from save requests if you want to restore the same files as were previously saved. Finally, all objects have a description attribute in which you can enter a text string to describe the object. This attribute is not interpreted by either ABS or MDMS, so you can use it for any purpose you see fit. By default, the description is blank. The following sections discusses all seven ABS objects in detail. Archives define the media type and characteristics about where backup data is stored. Each save and restore uses exactly one archive, except that certain complex save and restores can use two archives (see Section 3.3, Cataloging Existing Savesets). You can use a single archive for many different saves and restores by simply referencing the archive in the save and restore request. ABS defines four archives by default, which you can use in your save and restore requests as needed: • SYSTEM_BACKUPS - For system backups that are normally performed by a system administrator at regularly scheduled times • USER_BACKUPS - For backups performed by a non-privileged user to save or restore his or her own data • UNIX_BACKUPS - For backups of UNIX client data, normally performed by a system administrator • DISASTER_RECOVERY - For backups primarily designated for disaster recovery Although these default archives are provided by ABS, you may modify them as needed to suit your site’s operational environment. Alternatively, you can create your own archives and manipulate the attributes as described in the following sections. Saving and Restoring Data 3–1

Overview<br />

2.9 Getting Started<br />

Be<strong>for</strong>e creating save or res<strong>to</strong>re requests, you should first configure the media management environment.<br />

This includes the tape volumes, drives, jukeboxes and other media management<br />

objects that you may want <strong>to</strong> use. The recommended way <strong>to</strong> do this is <strong>to</strong> run the MDMS configuration<br />

command procedure, which offers an online tu<strong>to</strong>rial and help in defining the configuration.<br />

During execution of this procedure, type “?” <strong>to</strong> get help on any question, and type “??” <strong>to</strong><br />

get help and (in many cases) a list of existing objects or possible values <strong>for</strong> answers <strong>to</strong> questions.<br />

To invoke this procedure:<br />

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

A complete example of running this procedure is provided in Appendix A.<br />

Having completed the media management configuration, creating a save or res<strong>to</strong>re request in<br />

ABS can be very simple if you elect <strong>to</strong> use the default archives, environments and selection<br />

objects. The minimum amount of in<strong>for</strong>mation you need <strong>to</strong> specify <strong>for</strong> a save or res<strong>to</strong>re request is:<br />

• The name of the save or res<strong>to</strong>re.<br />

• The disks or files <strong>to</strong> be saved.<br />

• The start time of the save.<br />

ABS tries <strong>to</strong> determine the type of data being saved based on the <strong>for</strong>mat of the file specification<br />

and assigns by default a relevant archive and environment. So, <strong>for</strong> example, a save request can<br />

be specified and executed in a single DCL command as follows:<br />

$ MDMS CREATE SAVE MY_SAVE/INCLUDE=DISK$USER1:[SMITH...]/START<br />

This command creates a save called MY_SAVE, includes the file specification<br />

DISK$USER1:[SMITH...] (all files), and starts the save immediately. MDMS determines that<br />

this is a save of VMS files based on the file <strong>for</strong>mat, and assigns archive SYSTEM_BACKUPS<br />

and environment SYSTEM_BACKUPS_ENV, and creates a default selection and schedule.<br />

With this save definition, a default frequency of ONE_TIME_ONLY is assigned, and the save is<br />

not scheduled <strong>for</strong> regular execution.<br />

A res<strong>to</strong>re can also be defined. For example, <strong>to</strong> res<strong>to</strong>re the same files that were saved in<br />

MY_SAVE, you can enter the following command:<br />

$ MDMS CREATE RESTORE MY_RESTORE/INCLUDE=DISK$USER1:[SMITH...]/START<br />

This command creates a res<strong>to</strong>re called MY_RESTORE, includes the file specification<br />

DISK$USER1:[SMITH...] (all files), and starts the res<strong>to</strong>re immediately. MDMS determines that<br />

this is a res<strong>to</strong>re of VMS files based on the file <strong>for</strong>mat, and assigns archive SYSTEM_BACKUPS<br />

and environment SYSTEM_BACKUPS_ENV, and creates a default selection and schedule.<br />

With this res<strong>to</strong>re definition, a default frequency of ONE_TIME_ONLY is assigned, and the<br />

res<strong>to</strong>re is not scheduled <strong>for</strong> regular execution.<br />

Note<br />

Define the logical referring <strong>to</strong> the disk name be<strong>for</strong>e executing the res<strong>to</strong>re request. For<br />

more in<strong>for</strong>mation, see the note given in Section 3.5.8, “Destination (Res<strong>to</strong>re Only)”.<br />

Since these requests were defined with a frequency of ONE_TIME_ONLY, ABS will au<strong>to</strong>matically<br />

delete them after a default interval of 3 days after execution.<br />

Of course, creating the backup environment <strong>to</strong> backup all data in your production environment<br />

will involve more complex definitions, including creating your own archives, environments and<br />

in some cases selections and schedules. Chapter 3, Saving and Res<strong>to</strong>ring Data, describes all the<br />

ABS objects in detail.<br />

2-12 Overview

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

Saved successfully!

Ooh no, something went wrong!