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.

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

3.6 Selections<br />

– Oracle Rdb S<strong>to</strong>rage Area - These options (which are version-number specific) specify<br />

that you wish <strong>to</strong> back up selected s<strong>to</strong>rage areas of an Rdb database. In this case specify<br />

both the database file name(s) and selected s<strong>to</strong>rage areas.<br />

– UNIX Files - This option applies <strong>to</strong> saving or res<strong>to</strong>ring UNIX files on a client node.<br />

Enter a filesystem name in the <strong>for</strong>mat “/usr/...” <strong>to</strong> the level of granularity you want.<br />

With this option you must specify a SOURCE_NODE, which is the name of the UNIX<br />

node on which the online data resides.<br />

– Windows Files - This options applies <strong>to</strong> saving or res<strong>to</strong>ring Windows files on a client<br />

node. Enter a file pathname starting with the device (<strong>for</strong> example: C:\Windows\...” <strong>to</strong><br />

the level of granularity you want. With this option you must specify a<br />

SOURCE_NODE, which is the name of the Windows node on which the online data<br />

resides.<br />

• SOURCE NODE - This attribute applies <strong>to</strong> data types UNIX FILES and WINDOWS files<br />

only, and specifies the name of the node on which the file data resides. For other data types,<br />

the node is specified through the nodes and groups attributes in the request.<br />

The following table shows examples of the appropriate file, disk, path or database names that are<br />

valid <strong>for</strong> each data type:<br />

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

Data Type Examples Case Sensitive<br />

VMS Files<br />

Oracle Rdb Databases<br />

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

UNIX files<br />

Windows files<br />

$1$DUA420: (full disk, physical name)<br />

DISK$USER1: (full disk, logical name)<br />

DISK$USER1:[SMITH...]*.*;* (selective)<br />

DISK$USER1:[SMITH]LOGIN.COM;3 (file)<br />

Note: If the include specifications having<br />

“DISK$USER1” are <strong>for</strong> the res<strong>to</strong>re requests,<br />

then the logical “DISK$USER1” referring <strong>to</strong><br />

the disk name must be defined be<strong>for</strong>e executing<br />

the res<strong>to</strong>re request. For more in<strong>for</strong>mation,<br />

see the note given in the Section 3.5.8 “Destination<br />

(Res<strong>to</strong>re Only)” .<br />

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

Do not specify a version number.<br />

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

=BALANCES (saves)<br />

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

/AREA=BALANCES (res<strong>to</strong>res)<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 command line, you must<br />

enclose Windows specifications in quotes.<br />

No<br />

No<br />

No<br />

Yes<br />

No<br />

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

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

Saved successfully!

Ooh no, something went wrong!