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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.4.3 Compression<br />

3.4.4 Data Safety<br />

3.4.5 Drive Count<br />

Saving and Res<strong>to</strong>ring Data<br />

3.4 Environments<br />

• RECORD_DATE - Modify the BACKUP date <strong>to</strong> reflect the time that this file was backed<br />

up; this is the required option if you intend <strong>to</strong> do incremental backups of this file, and is the<br />

default value - supported <strong>for</strong> files of type VMS_FILES only.<br />

• NO_CHANGE - Do not change the online file at all. If this option is specified, you will not<br />

be able <strong>to</strong> per<strong>for</strong>m incremental saves on this file.<br />

• DELETE_FILE - This option is used when the backup is intended <strong>to</strong> be a long-term archive<br />

and you wish the file <strong>to</strong> be removed from the online system. The file is only deleted on a<br />

successful save operation.<br />

Although RECORD_DATE is supported <strong>for</strong> VMS_FILES only, it remains the default <strong>for</strong> all data<br />

types, and is simply ignored <strong>for</strong> the other types.<br />

ABS supports the following types of compression <strong>for</strong> UNIX clients:<br />

• No compression (default)<br />

• UNIX Compression<br />

• GZIP Compression<br />

It is recommended that you either use the default UNIX environment (UNIX_BACKUPS_ENV)<br />

or a single user-created environment <strong>for</strong> all your UNIX client saves, using a single type of compression<br />

<strong>for</strong> all UNIX saves. If you mix compression types among your UNIX saves, you should<br />

be very careful <strong>to</strong> assign the appropriate environment on any res<strong>to</strong>re. If you specify the wrong<br />

compression option on a res<strong>to</strong>re, then ABS will not be able <strong>to</strong> res<strong>to</strong>re the data. The default is no<br />

compression.<br />

The environment object allows you <strong>to</strong> specify one or more data safety features <strong>to</strong> ensure the reliability<br />

of the data on your offline tape volumes. You can select one or more of the following<br />

options:<br />

CRC - Per<strong>for</strong>ms a Cyclic Redundancy check and writes it <strong>for</strong> each data block on a tape volume.<br />

This enables detection of a bad block during a res<strong>to</strong>re operation.<br />

FULL_VERIFY - Rereads all saved data and compares <strong>to</strong> what is on disk during a save. This<br />

option approximately doubles the time <strong>for</strong> the data copy phase of a save operation.<br />

XOR - If the CRC check detects a bad block during a res<strong>to</strong>re operation, the XOR mechanism<br />

allows recovery of the block. This option is applicable only <strong>to</strong> data type VMS_FILES, <strong>for</strong> which<br />

the backup agent is VMS BACKUP.<br />

By default, all three options are enabled <strong>for</strong> maximum data safety.<br />

The drive count specifies the number of tape drives <strong>to</strong> use <strong>for</strong> each save or res<strong>to</strong>re using this<br />

environment. If there are at least as many drives available as the drive count, that number of<br />

drives are allocated <strong>for</strong> each save and res<strong>to</strong>re request. If not, a reduced number of drives are allocated.<br />

The default and highly recommended value is 1. The number of drives may range from 1 <strong>to</strong> 32.<br />

3.4.6 Prologue and Epilogue<br />

The prologue and epilogue attributes in the environment allow you <strong>to</strong> invoke a command procedure<br />

be<strong>for</strong>e and/or after the entire save or res<strong>to</strong>re request. This allows you <strong>to</strong> per<strong>for</strong>m pre-processing<br />

and post-processing operations around the entire request. Compare the order of<br />

Saving and Res<strong>to</strong>ring Data 3–13

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

Saved successfully!

Ooh no, something went wrong!