06.11.2014 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Overview<br />

2.2 ABS Objects<br />

2.2.1 Saves<br />

2.2.2 Res<strong>to</strong>res<br />

A save request defines the data <strong>to</strong> be saved and executes upon immediate invocation or through<br />

an au<strong>to</strong>matic, repetitive schedule. You can create save requests using either the MDMSView<br />

GUI or the CLI interface.<br />

A save defines the following criteria:<br />

• The data <strong>to</strong> back up - you can specify disks, files or databases <strong>to</strong> back up<br />

• The type of data <strong>to</strong> back up (VMS files, Oracle Rdb databases or s<strong>to</strong>rage areas, UNIX files<br />

or Windows files)<br />

• Whether the save is an incremental operation based on a previous save, or otherwise<br />

• When <strong>to</strong> save the data (base date and frequency)<br />

• Where <strong>to</strong> save the data (which archive <strong>to</strong> use)<br />

• The length of time <strong>to</strong> keep the data (retention period or expiration date)<br />

• Who can access a save request (<strong>for</strong> data safety)<br />

• What environment <strong>to</strong> use <strong>to</strong> execute the save request<br />

• Whether <strong>to</strong> per<strong>for</strong>m pre- or postprocessing commands<br />

To meet your site’s backup requirements, you will need <strong>to</strong> create save requests that fulfill those<br />

requirements.<br />

A res<strong>to</strong>re request res<strong>to</strong>res data from an archive back <strong>to</strong> online s<strong>to</strong>rage. You can create res<strong>to</strong>re<br />

requests using either the MDMSView GUI or the CLI interface. Res<strong>to</strong>re requests can be executed<br />

immediately or at a specified time. You can also schedule res<strong>to</strong>res <strong>for</strong> repeated operations<br />

in the same manner as saves.<br />

A res<strong>to</strong>re defines the following criteria:<br />

• The data <strong>to</strong> res<strong>to</strong>re - you can specify disks, files or databases <strong>to</strong> res<strong>to</strong>re<br />

• The type of data <strong>to</strong> res<strong>to</strong>re (VMS files, Oracle Rdb databases or s<strong>to</strong>rage areas, UNIX files or<br />

Windows files)<br />

• Whether the res<strong>to</strong>re is an incremental res<strong>to</strong>re based on a previous res<strong>to</strong>re, or otherwise<br />

• Where <strong>to</strong> res<strong>to</strong>re the data (optional output location other than the original location)<br />

• Where the data resides (on which archive)<br />

• Who can access a res<strong>to</strong>re request (<strong>for</strong> data security)<br />

• What environment <strong>to</strong> use <strong>to</strong> execute the res<strong>to</strong>re request<br />

• Whether <strong>to</strong> per<strong>for</strong>m pre- or postprocessing commands<br />

To meet your s<strong>to</strong>rage management requirements, you will need <strong>to</strong> create res<strong>to</strong>re requests that fulfill<br />

those requirements.<br />

Figure 2–1 illustrates the path of a save or res<strong>to</strong>re request.<br />

2-2 Overview

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

Saved successfully!

Ooh no, something went wrong!