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.5 Saves and Restores – 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. – 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 option 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. – VMS Saveset cataloging - This option applies to cataloging existing VMS Backup saveset from tapes. Enter the tape name followed by a colon (:) and the saveset name (or wildcard). See Section 3.3 for more information on this functionality. • 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–3 Disk, File, Path and Database Specification Formats Data Type Examples Case Sensitive VMS Files Oracle Rdb Databases $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. No No 3-20 Saving and Restoring Data

Table 3–3 Disk, File, Path and Database Specification Formats Saving and Restoring Data 3.5 Saves and Restores Data Type Examples Case Sensitive Oracle Rdb Storage Areas UNIX files Windows files DISK2:[RDB]ACCOUNTS.RDB/INCLUDE =BALANCES (save) DISK2:[RDB]ACCOUNTS.RDB /AREA=BALANCES (restore) 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 CLI, you must enclose Windows specifications in quotes. No Yes No VMS saveset cataloging tape_name:saveset_name No Note Wildcards are not allowed in the include specification for WINDOWS_FILES and UNIX_FILES data type in a save request. If you prefer to use selection objects directly (which enable you to specify additional selection criteria), then create a selection as shown in Section 3.3.3, then include the selection in the SELECTIONS attribute in the save or restore request. You can include up to 24 selections in a save or restore request with the caveat that a maximum of 24 disk, file or database file specifications (in total) are supported in a single save or restore request. 3.5.7 Delete Interval and Keep Some saves and most restores are intended to be run only once, and have a frequency of ONE TIME ONLY. With this in mind, ABS automatically deletes such requests after a defined interval after the request has executed. This interval is the delete interval and can be customized for each save and restore request. If not specified, all ONE TIME ONLY requests are deleted approximately 3 days after execution: the actual delete is performed by a daily scheduled activity which runs at a certain time every day. If the frequency is something other than ONE TIME ONLY, ABS does not automatically delete the request. If the delete interval is set to NONE, then the request is deleted the next time the scheduled activity runs after execution of the request. If you do not wish to have these requests automatically deleted, then set the keep attribute. This flags the request to be kept indefinitely and clears the delete interval. 3.5.8 Destination (Restore Only) ABS allows you to restore data to a different disk, directory, file system or pathname from where the data was saved. This is useful if you wish to make additional copies of data from the archive. If you wish to restore to a different location, enter the disk, directory, file system or pathname in the destination attribute of the restore. If not specified, the data is restored to the original source location of the data. Saving and Restoring Data 3–21

Table 3–3 Disk, File, Path and Database Specification Formats<br />

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

3.5 Saves and Res<strong>to</strong>res<br />

Data Type Examples Case Sensitive<br />

Oracle Rdb S<strong>to</strong>rage Areas<br />

UNIX files<br />

Windows files<br />

DISK2:[RDB]ACCOUNTS.RDB/INCLUDE<br />

=BALANCES (save)<br />

DISK2:[RDB]ACCOUNTS.RDB<br />

/AREA=BALANCES (res<strong>to</strong>re)<br />

Do not specify a version number - the include<br />

syntax is required, even from the GUI. If<br />

entered from the CLI, you must enclose the<br />

specification in quotes.<br />

/usr/smith/<br />

If entered from the CLI, you must enclose<br />

UNIX specification in quotes.<br />

C:\WINNT\SMITH\<br />

If entered from the CLI, you must enclose<br />

Windows specifications in quotes.<br />

No<br />

Yes<br />

No<br />

VMS saveset cataloging tape_name:saveset_name No<br />

Note<br />

Wildcards are not allowed in the include specification <strong>for</strong> WINDOWS_FILES and<br />

UNIX_FILES data type in a save request.<br />

If you prefer <strong>to</strong> use selection objects directly (which enable you <strong>to</strong> specify additional selection<br />

criteria), then create a selection as shown in Section 3.3.3, then include the selection in the<br />

SELECTIONS attribute in the save or res<strong>to</strong>re request. You can include up <strong>to</strong> 24 selections in a<br />

save or res<strong>to</strong>re request with the caveat that a maximum of 24 disk, file or database file specifications<br />

(in <strong>to</strong>tal) are supported in a single save or res<strong>to</strong>re request.<br />

3.5.7 Delete Interval and Keep<br />

Some saves and most res<strong>to</strong>res are intended <strong>to</strong> be run only once, and have a frequency of ONE<br />

TIME ONLY. With this in mind, ABS au<strong>to</strong>matically deletes such requests after a defined interval<br />

after the request has executed. This interval is the delete interval and can be cus<strong>to</strong>mized <strong>for</strong> each<br />

save and res<strong>to</strong>re request. If not specified, all ONE TIME ONLY requests are deleted approximately<br />

3 days after execution: the actual delete is per<strong>for</strong>med by a daily scheduled activity which<br />

runs at a certain time every day. If the frequency is something other than ONE TIME ONLY,<br />

ABS does not au<strong>to</strong>matically delete the request. If the delete interval is set <strong>to</strong> NONE, then the<br />

request is deleted the next time the scheduled activity runs after execution of the request.<br />

If you do not wish <strong>to</strong> have these requests au<strong>to</strong>matically deleted, then set the keep attribute. This<br />

flags the request <strong>to</strong> be kept indefinitely and clears the delete interval.<br />

3.5.8 Destination (Res<strong>to</strong>re Only)<br />

ABS allows you <strong>to</strong> res<strong>to</strong>re data <strong>to</strong> a different disk, direc<strong>to</strong>ry, file system or pathname from where<br />

the data was saved. This is useful if you wish <strong>to</strong> make additional copies of data from the archive.<br />

If you wish <strong>to</strong> res<strong>to</strong>re <strong>to</strong> a different location, enter the disk, direc<strong>to</strong>ry, file system or pathname in<br />

the destination attribute of the res<strong>to</strong>re. If not specified, the data is res<strong>to</strong>red <strong>to</strong> the original source<br />

location of the data.<br />

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

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

Saved successfully!

Ooh no, something went wrong!