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

Saving and Restoring Data 3.6 Selections Although ABS passes information that you specify in the save, restore and environment to the backup agent, you can pass qualifiers directly to the backup agent using the agent qualifiers attribute. Refer to the appropriate backup agent documentation for information on these qualifiers. 3.6.2 Before Date, Since Date and Date Type (Saves Only) For save requests, you can select files for saving based on the date files were last modified. You can specify either or both of the following: • Before Date - Any version of the file modified before the specified date • Since Date - Any version of the file modified after the specified date If you specify both a before and since date, you are providing a range of dates in which to select files. If a file does not have a revision date (modified date), then ABS uses the creation date instead. ABS does not yet support the date type attribute, which would allow you to select any one of the four online dates maintained by OpenVMS. 3.6.3 Conflict Options (Restore Only) When restoring files, you may find that there are files of the same name already located in the destination directory or original source location. You can specify what ABS should do if it encounters this situation by specifying one of the following conflict options: • NEW VERSION - Restores the data and header and creates a new version of the file - applicable to VMS files only. • OVERLAY VERSION - Overwrites the online version with the archive version of the data, but keeps the online version of the header. • REPLACE VERSION - Deletes the online version of the file, and restores both the header and data from the archive. • RETAIN VERSION - Keeps the online version of the header and data and does not restore the file from the archive. If not specified, the default is RETAIN VERSION. 3.6.4 Include, Exclude, Data Type and Source Node In exactly the same manner as in save and restore requests, you can specify the following attributes in selection objects directly: • INCLUDE - A list of disks, files, paths or databases to include in the save or restore. If you want the file directory structure to be maintained during the restore operation, see the note given in Section 3.5.6 “Include, Exclude, Data Type and Source Node” . • EXCLUDE - A list of files to exclude from the save or restore that would otherwise have been included according to the include specification. This option applies to data type VMS FILES only • DATA TYPE - The type of data to be saved or restored - select one of the following: – VMS Files - Applicable to VMS files. If only a disk is selected, a FULL backup of the entire disk is performed. If directory and file specifications are specified, then a SELECTIVE backup of files is performed. – Oracle Rdb Database Options - These options (which are version-number specific) specify that you wish to back up an entire Rdb database using the RMU backup utility. In this case, specify the name of the Rdb database files. 3-30 Saving and Restoring Data

Saving and Restoring Data 3.6 Selections – Oracle Rdb Storage Area - These options (which are version-number specific) specify that you wish to back up selected storage areas of an Rdb database. In this case specify both the database file name(s) and selected storage areas. – UNIX Files - This option applies to saving or restoring UNIX files on a client node. Enter a filesystem name in the format “/usr/...” to the level of granularity you want. With this option you must specify a SOURCE_NODE, which is the name of the UNIX node on which the online data resides. – Windows Files - This options applies to saving or restoring Windows files on a client node. Enter a file pathname starting with the device (for example: C:\Windows\...” to the level of granularity you want. With this option you must specify a SOURCE_NODE, which is the name of the Windows node on which the online data resides. • SOURCE NODE - This attribute applies to data types UNIX FILES and WINDOWS files only, and specifies the name of the node on which the file data resides. For other data types, the node is specified through the nodes and groups attributes in the request. The following table shows examples of the appropriate file, disk, path or database names that are valid for each data type: Table 3–5 Disk, File, Path and Database Specification Formats Data Type Examples Case Sensitive VMS Files Oracle Rdb Databases Oracle Rdb Storage Areas UNIX files Windows files $1$DUA420: (full disk, physical name) DISK$USER1: (full disk, logical name) DISK$USER1:[SMITH...]*.*;* (selective) DISK$USER1:[SMITH]LOGIN.COM;3 (file) Note: If the include specifications having “DISK$USER1” are for the restore requests, then the logical “DISK$USER1” referring to the disk name must be defined before executing the restore request. For more information, see the note given in the Section 3.5.8 “Destination (Restore Only)” . DISK2:[USER_RDB]ACCOUNTS.RDB Do not specify a version number. DISK2:[RDB]ACCOUNTS.RDB/INCLUDE =BALANCES (saves) DISK2:[RDB]ACCOUNTS.RDB /AREA=BALANCES (restores) Do not specify a version number - the include syntax is required, even from the GUI. If entered from the CLI, you must enclose the specification in quotes. /usr/smith/* If entered from the CLI, you must enclose UNIX specification in quotes. C:\WINNT\SMITH\* If entered from the command line, you must enclose Windows specifications in quotes. No No No Yes No Saving and Restoring Data 3–31

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

3.6 Selections<br />

Although ABS passes in<strong>for</strong>mation that you specify in the save, res<strong>to</strong>re and environment <strong>to</strong> the<br />

backup agent, you can pass qualifiers directly <strong>to</strong> the backup agent using the agent qualifiers<br />

attribute. Refer <strong>to</strong> the appropriate backup agent documentation <strong>for</strong> in<strong>for</strong>mation on these qualifiers.<br />

3.6.2 Be<strong>for</strong>e Date, Since Date and Date Type (Saves Only)<br />

For save requests, you can select files <strong>for</strong> saving based on the date files were last modified. You<br />

can specify either or both of the following:<br />

• Be<strong>for</strong>e Date - Any version of the file modified be<strong>for</strong>e the specified date<br />

• Since Date - Any version of the file modified after the specified date<br />

If you specify both a be<strong>for</strong>e and since date, you are providing a range of dates in which <strong>to</strong> select<br />

files. If a file does not have a revision date (modified date), then ABS uses the creation date<br />

instead.<br />

ABS does not yet support the date type attribute, which would allow you <strong>to</strong> select any one of the<br />

four online dates maintained by <strong>OpenVMS</strong>.<br />

3.6.3 Conflict Options (Res<strong>to</strong>re Only)<br />

When res<strong>to</strong>ring files, you may find that there are files of the same name already located in the<br />

destination direc<strong>to</strong>ry or original source location. You can specify what ABS should do if it<br />

encounters this situation by specifying one of the following conflict options:<br />

• NEW VERSION - Res<strong>to</strong>res the data and header and creates a new version of the file - applicable<br />

<strong>to</strong> VMS files only.<br />

• OVERLAY VERSION - Overwrites the online version with the archive version of the data,<br />

but keeps the online version of the header.<br />

• REPLACE VERSION - Deletes the online version of the file, and res<strong>to</strong>res both the header<br />

and data from the archive.<br />

• RETAIN VERSION - Keeps the online version of the header and data and does not res<strong>to</strong>re<br />

the file from the archive.<br />

If not specified, the default is RETAIN VERSION.<br />

3.6.4 Include, Exclude, Data Type and Source Node<br />

In exactly the same manner as in save and res<strong>to</strong>re requests, you can specify the following<br />

attributes in selection objects directly:<br />

• INCLUDE - A list of disks, files, paths or databases <strong>to</strong> include in the save or res<strong>to</strong>re. If you<br />

want the file direc<strong>to</strong>ry structure <strong>to</strong> be maintained during the res<strong>to</strong>re operation, see the note<br />

given in Section 3.5.6 “Include, Exclude, Data Type and Source Node” .<br />

• EXCLUDE - A list of files <strong>to</strong> exclude from the save or res<strong>to</strong>re that would otherwise have<br />

been included according <strong>to</strong> the include specification. This option applies <strong>to</strong> data type VMS<br />

FILES only<br />

• DATA TYPE - The type of data <strong>to</strong> be saved or res<strong>to</strong>red - select one of the following:<br />

– VMS Files - Applicable <strong>to</strong> VMS files. If only a disk is selected, a FULL backup of the<br />

entire disk is per<strong>for</strong>med. If direc<strong>to</strong>ry and file specifications are specified, then a<br />

SELECTIVE backup of files is per<strong>for</strong>med.<br />

– Oracle Rdb Database Options - These options (which are version-number specific)<br />

specify that you wish <strong>to</strong> back up an entire Rdb database using the RMU backup utility.<br />

In this case, specify the name of the Rdb database files.<br />

3-30 Saving and Res<strong>to</strong>ring Data

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

Saved successfully!

Ooh no, something went wrong!