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 • Defining the date and time to be used as a basis for scheduling - all scheduling intervals are based on both the date portion and time portion of the base date, and anniversaries of the base date at intervals defined by the frequency attribute. • Defining the basis for full versus incremental saves for complex frequencies such as dailyfull-weekly, log_2 and log_3. The base date and appropriate anniversaries of the base date define the date of the full saves. Unless you want to change the scheduling or save type basis for the request, you would not change the base date. As such, the base date will remain a date in the past. Compare this to the start date, which specifies the next start date and time for the request. The start date is updated whenever the request is run to reflect the next time it is scheduled, or NONE if it is not scheduled again. When a request is first created, and you specify only one of the dates, both dates are set (i.e. the next start date is the base date). By default, neither a base date or start date are supplied so the request is not scheduled for execution. You can use the start date and skip time to request a one-time special, or non-scheduled, execution of the request. For example, assume that the normal scheduled time for a request is 23:00, as specified in the base date. However, you know that this is a particularly busy night and you want to start this request for tonight only at 21:00 instead. You can do this by setting the start date to 21:00. However, when the request is rescheduled, it will be rescheduled to the next iteration of the base date, or 23:00 the same day. You probably do not want this, so to avoid it you can set the start date together with a skip time to avoid running the request twice. The skip time is an exclusion time (expressed as a delta time) from the specified start date in which the request will not be rescheduled: normally you can set this to one day to avoid running the request twice in the same day. The following table shows some examples of base date, start date and skip time definitions based on a daily frequency: Table 3–2 Use of Base Date, Start Date and Skip Time Base Date Start Date Skip Time Next Start 23-Aug 23:00 10-Sep 21:00 None 10-Sep 23:00 23-Aug 23:00 10-Sep 21:00 1-00:00:00 11-Sep 23:00 23-Aug-23:00 10-Sep-23:00 2-00:00:00 12-Sep 23:00 When you specify a skip time, ABS saves it in the database until the request is next rescheduled. When the rescheduling takes place, the skip time is applied to the calculation, then cleared from the database. If you set a skip time and do not see it in the request, then it has already been applied to the next start date. 3.5.4 Before Date, Since Date and Date Archived (Restore Only) When restoring files, you can choose a specific iteration of the files based on their archive date - that is, the date that they were saved in the archive. If you know the exact date archived, use the data archived attribute. If you know only an approximate date archived, use the before or since attributes to specify a range of dates. So, for example, if you wish to restore a file as it existed in the first week of January, you can specify a before date of the 8th January (at midnight), or a since date of 1st January (at midnight). When determining appropriate before or since dates, you should probably lookup the files in the catalog before requesting a restore, so that you can specify before and since dates that uniquely identify a single iteration of the file to restore. 3-18 Saving and Restoring Data

Saving and Restoring Data 3.5 Saves and Restores The before and since dates in the restore apply only to the archive date of the file. They are not related to the before and since dates in the selection object, which refer to files’ online dates that are maintained by OpenVMS. 3.5.5 Catalog (Restore Only) On a restore, you can specify a catalog name instead of an archive name if you know the name of the catalog from which to locate the restore information, and do not know the name of the archive. Normally, however, you would specify the archive under which the data was saved rather than the catalog. 3.5.6 Include, Exclude, Data Type and Source Node One of the more obvious attributes of a save or restore request are the file names, disk names path names or database names that you wish to save or restore. There are two options for specifying these names in a save or restore request: • In an INCLUDE specification - You can specify the names directly in the save or restore request in an INCLUDE specification. You can specify multiple disks and/or files in a comma-separated list with the restriction that all disk and file specifications relate to a single data type (for example, VMS files). If you wish to mix file types in a single save or restore request (for example, VMS files and Windows files), then you must use the second option. Note In case the include specification in the Save request had a directory tree structure, then to maintain the same during the Restore operation, you must specify the wildcard “*” in the include specification of the Restore request. Example: /Include = TPRD:[TPRD.APPFILES*]*.*;* If you do not use the wildcard “*” or specify a wildcard other than “*” in the include specification, then all the files are automatically restored to the root directory. Examples: /Include = TPRD:[TPRD.APPFILES]*.*;* /Include = TPRD:[TPRD.APPFILES%]*.*;* • Using SELECTIONS - With this option, you create selection objects directly using the MDMSView GUI or the CLI, specify the appropriate include specifications, then associate the selection object(s) with the save or restore. You can associate multiple selection objects with any save or restore request as long as the total number of disk, file, path or database specifications in all the selection objects does not exceed 24. When you specify disk, file and database names by including them in the save and restore request, then you are effectively creating a default selection object. This selection object has the same name as the save or restore, with the suffix “_SAVE_SEL_DEL” or “_REST_SEL_DEF” respectively. You can specify the following attributes directly in the save or restore request for inclusion in the default selection: • INCLUDE - A list of disks, files, paths or databases to include in the save or restore. • 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: Saving and Restoring Data 3–19

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

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

The be<strong>for</strong>e and since dates in the res<strong>to</strong>re apply only <strong>to</strong> the archive date of the file. They are not<br />

related <strong>to</strong> the be<strong>for</strong>e and since dates in the selection object, which refer <strong>to</strong> files’ online dates that<br />

are maintained by <strong>OpenVMS</strong>.<br />

3.5.5 Catalog (Res<strong>to</strong>re Only)<br />

On a res<strong>to</strong>re, you can specify a catalog name instead of an archive name if you know the name of<br />

the catalog from which <strong>to</strong> locate the res<strong>to</strong>re in<strong>for</strong>mation, and do not know the name of the<br />

archive. Normally, however, you would specify the archive under which the data was saved<br />

rather than the catalog.<br />

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

One of the more obvious attributes of a save or res<strong>to</strong>re request are the file names, disk names<br />

path names or database names that you wish <strong>to</strong> save or res<strong>to</strong>re. There are two options <strong>for</strong> specifying<br />

these names in a save or res<strong>to</strong>re request:<br />

• In an INCLUDE specification - You can specify the names directly in the save or res<strong>to</strong>re<br />

request in an INCLUDE specification. You can specify multiple disks and/or files in a<br />

comma-separated list with the restriction that all disk and file specifications relate <strong>to</strong> a single<br />

data type (<strong>for</strong> example, VMS files). If you wish <strong>to</strong> mix file types in a single save or<br />

res<strong>to</strong>re request (<strong>for</strong> example, VMS files and Windows files), then you must use the second<br />

option.<br />

Note<br />

In case the include specification in the Save request had a direc<strong>to</strong>ry tree structure, then<br />

<strong>to</strong> maintain the same during the Res<strong>to</strong>re operation, you must specify the wildcard “*”<br />

in the include specification of the Res<strong>to</strong>re request.<br />

Example: /Include = TPRD:[TPRD.APPFILES*]*.*;*<br />

If you do not use the wildcard “*” or specify a wildcard other than “*” in the include<br />

specification, then all the files are au<strong>to</strong>matically res<strong>to</strong>red <strong>to</strong> the root direc<strong>to</strong>ry.<br />

Examples:<br />

/Include = TPRD:[TPRD.APPFILES]*.*;*<br />

/Include = TPRD:[TPRD.APPFILES%]*.*;*<br />

• Using SELECTIONS - With this option, you create selection objects directly using the<br />

MDMSView GUI or the CLI, specify the appropriate include specifications, then associate<br />

the selection object(s) with the save or res<strong>to</strong>re. You can associate multiple selection objects<br />

with any save or res<strong>to</strong>re request as long as the <strong>to</strong>tal number of disk, file, path or database<br />

specifications in all the selection objects does not exceed 24.<br />

When you specify disk, file and database names by including them in the save and res<strong>to</strong>re<br />

request, then you are effectively creating a default selection object. This selection object has the<br />

same name as the save or res<strong>to</strong>re, with the suffix “_SAVE_SEL_DEL” or “_REST_SEL_DEF”<br />

respectively. You can specify the following attributes directly in the save or res<strong>to</strong>re request <strong>for</strong><br />

inclusion in the default selection:<br />

• INCLUDE - A list of disks, files, paths or databases <strong>to</strong> include in the save or res<strong>to</strong>re.<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 />

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

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

Saved successfully!

Ooh no, something went wrong!