HP Archive Backup System for OpenVMS Guide to Operations
Share Embed Flag
Download ePaper

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 3.5.12 Nodes and Groups By default, saves and restores are not flagged as incremental. If you wish to define an incremental save or restore, then set the incremental attribute. It is important to point out that if you execute an incremental save 127 times in a row without an intervening FULL save, then the 128th “incremental” save will actually be a full save. This rule actually applies to each individual file, disk, path or database specification within the save request, and as such, it is possible for the various files, disks, paths or databases within a single save request to be backed up at different incremental levels, or have a mixture of fulls and incrementals. As such, it is recommended that you intersperse a non-incremental (full) save at least once a week to avoid unexpected full backups on saves/restores marked incremental and to reduce the restore time required with a large number of incrementals. If you are mixing FULL and INCREMENTAL save requests, use the same catalog for both save requests so that the FULL catalog entry will be found and used as a base for the incrementals. ABS always performs save and restore operations on an OpenVMS execution node, under the control of the ABS coordinator process. Only one execution node actually executes any particular save or restore request at a particular time, but you can specify a list of compatible nodes using either the nodes or groups attributes. At execution time, the node list or group list is scanned in order to determine the execution node, and ABS will attempt to schedule the operation on the first such node. If ABS fails to establish a connection to that node, it will try the next node on the list, and so on until the request is successfully submitted. For data types VMS files and Oracle databases of all types, the execution node is also the node where the data resides. Therefore, all execution nodes or groups must have access to the data being saved or restored. For data types UNIX files and Windows files, the execution node is the node running the ABS coordinator process, not the UNIX or Windows node on which the data resides: that node is specified by the SOURCE NODE attribute in the save or restore (or selection). If you wish to enter nodes individually, enter a comma-separated list of nodes in the NODES attribute or select a list of nodes from the GUI. Enter the MDMS node object name (which should be the same as the DECnet Phase IV name if DECnet is running) - do not specify the TCP/IP name or DECnet Phase V fullname. MDMS supports the notion of groups, whereby you can associate a list of nodes which have something in common (for example, nodes in a cluster) into a group, and simply reference the group name. In this case, you can simply enter one or more group names in the GROUPS attribute. The NODES attribute and GROUPS attribute are mutually exclusive - you have to choose which one to enter. If you enter neither nodes nor groups, then ABS enters the node from which the save or restore was created in the NODES attribute. 3.5.13 Prologue and Epilogue The prologue and epilogue attributes in the save or restore request allow you to invoke a command procedure before and/or after each disk, file, path or database specification in the request. This allows you to perform pre-processing and post-processing operations around individual save or restore iterations. Compare the order of save and restore prologue and epilogue procedures operations to the environment prologue and epilogue procedures, which are executed before and/or after the entire save or restore request. The order of execution is illustrated below: • Environment prologue • Start save or restore request 3-26 Saving and Restoring Data

• First disk/file specification prologue • First disk/file specification save or restore operation • First disk/file specification epilogue • Next disk/file specification prologue • Next disk/file specification save or restore operation • Next disk/file specification epilogue • ...... • End save or restore request • Environment epilogue (only on successful completion) Saving and Restoring Data 3.5 Saves and Restores ABS defines logical names that can be used within the prologue or epilogue command procedures. Each name is suffixed by “_n”, where n is the iteration number for each include disk, file, path or database specification. The value for n starts at 1 and goes to 24, the maximum number of include specifications supported by ABS. These logical names are defined in the process job table as follows: Table 3–4 Logical Names in Save/Restore Prologues and Epilogues Logical Name ABS_OS_OBJECT_SET_n ABS_OS_OBJECT_TYPE_n ABS_OS_DMT_n ABS_OS_INCREMENTAL_LEVEL_n ABS_OS_VOLUME_SET_n ABS_OS_START_RVN_n ABS_OS_LAST_RVN_n ABS_OS_START_FILE_POSITION_n ABS_OS_SAVESET_NAME_n ABS_OS_SAVESET_FORMAT_n ABS_OS_STATUS_n Meaning The include disk, file, path or database name currently being processed The data type for the specification The type of operation: FULL, INCREMENTAL, SELECTIVE For an INCREMENTAL operation, the incremental level being preformed The volume set being used Starting relative volume number (RVN) of the volume set for the files being processed. The value is zero if the archive type is DISK, The last relative volume number in the volume set containing this specification. This value is valid for epilogue procedures only, and equates to “Not yet determined” for prologues. The value is zero if the archive type is DISK. The starting file position of the saveset on the tape volume. This indicates how many tape marks from the beginning of the tape need to be skipped to arrive at the file. The value is zero if the archive type is DISK. The name of the saveset being used. The format of the saveset: either VMS, gtar or RMU. The ABS status of the portion of the request for this specification Saving and Restoring Data 3–27

• First disk/file specification prologue<br />

• First disk/file specification save or res<strong>to</strong>re operation<br />

• First disk/file specification epilogue<br />

• Next disk/file specification prologue<br />

• Next disk/file specification save or res<strong>to</strong>re operation<br />

• Next disk/file specification epilogue<br />

• ......<br />

• End save or res<strong>to</strong>re request<br />

• Environment epilogue (only on successful completion)<br />

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

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

ABS defines logical names that can be used within the prologue or epilogue command procedures.<br />

Each name is suffixed by “_n”, where n is the iteration number <strong>for</strong> each include disk, file,<br />

path or database specification. The value <strong>for</strong> n starts at 1 and goes <strong>to</strong> 24, the maximum number<br />

of include specifications supported by ABS. These logical names are defined in the process job<br />

table as follows:<br />

Table 3–4 Logical Names in Save/Res<strong>to</strong>re Prologues and Epilogues<br />

Logical Name<br />

ABS_OS_OBJECT_SET_n<br />

ABS_OS_OBJECT_TYPE_n<br />

ABS_OS_DMT_n<br />

ABS_OS_INCREMENTAL_LEVEL_n<br />

ABS_OS_VOLUME_SET_n<br />

ABS_OS_START_RVN_n<br />

ABS_OS_LAST_RVN_n<br />

ABS_OS_START_FILE_POSITION_n<br />

ABS_OS_SAVESET_NAME_n<br />

ABS_OS_SAVESET_FORMAT_n<br />

ABS_OS_STATUS_n<br />

Meaning<br />

The include disk, file, path or database name<br />

currently being processed<br />

The data type <strong>for</strong> the specification<br />

The type of operation:<br />

FULL, INCREMENTAL, SELECTIVE<br />

For an INCREMENTAL operation, the incremental<br />

level being pre<strong>for</strong>med<br />

The volume set being used<br />

Starting relative volume number (RVN) of the<br />

volume set <strong>for</strong> the files being processed. The<br />

value is zero if the archive type is DISK,<br />

The last relative volume number in the volume<br />

set containing this specification. This value is<br />

valid <strong>for</strong> epilogue procedures only, and<br />

equates <strong>to</strong> “Not yet determined” <strong>for</strong> prologues.<br />

The value is zero if the archive type is DISK.<br />

The starting file position of the saveset on the<br />

tape volume. This indicates how many tape<br />

marks from the beginning of the tape need <strong>to</strong><br />

be skipped <strong>to</strong> arrive at the file. The value is<br />

zero if the archive type is DISK.<br />

The name of the saveset being used.<br />

The <strong>for</strong>mat of the saveset: either VMS, gtar or<br />

RMU.<br />

The ABS status of the portion of the request<br />

<strong>for</strong> this specification<br />

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

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!