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.1 Archives 3.1.1 Archive Name 3.1.2 Archive Type 3.1.3 Catalog 3.1.4 Consolidation This name is used to reference the archive in save and restore requests. There are no required or ad-hoc conventions for archive names, so they can reflect their usage in your environment. However, there are ad-hoc conventions for environment names based on the archive name, so you should restrict the archive name to 60 characters. ABS supports two types of archive, which are hopefully self-explanatory: • DISK - The archive data is stored on disk media, which can include optical disk. ABS assumes that all disk media are online and mounted on the OpenVMS system before any save or restore operation is executed. ABS does not perform any load/unload or mount operations on disk archives. When you specify disk archive type, the archive must contain a destination attribute indicating the disk and directory location of the archive data. • TAPE - The archive data is stored on tape media, and uses MDMS for media management control of the media. When you specify tape archive type, the archive must contain a media type (defined in MDMS) that defines the type of tape media to be used for the archive. Only a single media type is supported. In addition, the archive may optionally contain a pool specification (indicating a set of volumes reserved to users authorized for the pool) and a location specification (used to allocate a drive). A catalog contains information about what data is stored in the archive and where it is stored. Each archive uses exactly one catalog, although catalogs can be shared among different archives. ABS defines a default catalog called ABS_CATALOG, which is assigned to all archives by default if a different catalog is not specified. If you wish to define a different catalog for an archive, then specify a catalog object name (not its location) in the catalog attribute of the archive. For the archive to be useful, the catalog must be defined as a catalog object in MDMS. An archive with a name of “DISASTER_RECOVERY” is the only archive allowed to have no catalog associated with it and the save operation is therefore not catalogued (see Chapter 7, Preparing For Disaster Recovery). ABS supports the concept of consolidation criteria which determine when a volume set should be retired from use in the archive and a new volume set used. ABS supports three types of consolidation criteria, of which none, one, two or all three can be applicable: • INTERVAL - You can specify an interval as a delta time from the creation of the current volume set to the creation of the next volume set. The current volume set is retired if the consolidation interval is exceeded. • SAVESETS - You can specify the maximum number of savesets that should reside on the volume set. If this number would be exceeded, ABS retires the current volume set and allocates a new volume set for the archive. There is an ANSI-imposed maximum of 10000 savesets in a volume set • VOLUMES - A volume set can contain one or more physical tape volumes. You can limit the number of volumes by specifying volumes on the consolidation criteria. If this number would be exceeded, ABS retires the volume set and allocates a new volume set. There is an ANSI-imposed maximum limit of 100 volumes in a volume set. 3-2 Saving and Restoring Data

3.1.5 Destination 3.1.6 Drives 3.1.6.1 Drive selection Saving and Restoring Data 3.1 Archives If you specify multiple consolidation criteria, ABS creates a new volume set when the first of any of the defined criteria are exceeded. The default consolidation criteria is an INTERVAL of 7 days. If no consolidation criteria are specified, then ABS creates a new volume set when the ANSI limits apply, or upon the first error writing to the volume set. This is not recommended as you may create excessively large volume sets, and may have to split a volume set between onsite and offsite (vault) locations. Consolidation criteria are only applicable to an archive type of TAPE. If you specified an archive type of DISK, you must enter a destination attribute for the archive, or use the default of ABS$ROOT:[000000]. The destination contains the disk and directory location of the data saved in this disk archive. When specifying destination, you should ensure that the specified disk has enough free capacity to handle all data to be saved in this archive. ABS does not monitor the disk for sufficient capacity. ABS clears this attribute if the archive type is TAPE. Also, if you have specified a logical name as part of the destination name, then ensure that before the restore request is executed, the logical is defined as a concealed logical that is either defined as a system-wide logical name or just has the physical device name before the restore request is executed. If you do not want to use the logical name, then specify the physical device name followed by the directory path as the destination for the restore request. ABS allows you to enter a list of drives that can be used by save and restore operations to and from this archive. This should be used only to restrict the drives that would normally be available for these operations for some reason. Normally, you can let ABS select drives for all operations based on media type and location, and so you do not need to specify the drives in the archive. If you do specify drives, be aware that these drives apply to restores as well as saves. Drives are only applicable to an archive type of TAPE. When the drive list is specified in the archive class, the drive is allocated by ABS/MDMS for operation as below: 1. Volume-set is not present in the archive class ABS will allocate the first available drive and continues to select a volume matching the selection criteria. If all the drives in drive list are not free then ABS will Indefinitely loop for allocating the drives and wait for drive to be available. 2. When the volume set is present in the archive class and the required volume is present in: – Slot - then ABS selects the first available drive from the drive list. – Drive that is part of drive list in the archive class - In this condition the drive where the volume is currently present will be used for save operation. For example, if drive list consist of 2 drives A and B and if the required volume is present in B, then drive B will be used for the save/restore operation even if drive A comes first in the drive list. 3. Drive that is not a part of drive list - ABS will unload the volume from the drive and load the volume in first available drive in the drive list. Note The above allocation algorithm is applicable only when drive list is specified in the archive class. Saving and Restoring Data 3–3

3.1.5 Destination<br />

3.1.6 Drives<br />

3.1.6.1 Drive selection<br />

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

3.1 <strong>Archive</strong>s<br />

If you specify multiple consolidation criteria, ABS creates a new volume set when the first of<br />

any of the defined criteria are exceeded. The default consolidation criteria is an INTERVAL of 7<br />

days. If no consolidation criteria are specified, then ABS creates a new volume set when the<br />

ANSI limits apply, or upon the first error writing <strong>to</strong> the volume set. This is not recommended as<br />

you may create excessively large volume sets, and may have <strong>to</strong> split a volume set between onsite<br />

and offsite (vault) locations. Consolidation criteria are only applicable <strong>to</strong> an archive type of<br />

TAPE.<br />

If you specified an archive type of DISK, you must enter a destination attribute <strong>for</strong> the archive,<br />

or use the default of ABS$ROOT:[000000]. The destination contains the disk and direc<strong>to</strong>ry location<br />

of the data saved in this disk archive. When specifying destination, you should ensure that<br />

the specified disk has enough free capacity <strong>to</strong> handle all data <strong>to</strong> be saved in this archive. ABS<br />

does not moni<strong>to</strong>r the disk <strong>for</strong> sufficient capacity. ABS clears this attribute if the archive type is<br />

TAPE.<br />

Also, if you have specified a logical name as part of the destination name, then ensure that be<strong>for</strong>e<br />

the res<strong>to</strong>re request is executed, the logical is defined as a concealed logical that is either defined<br />

as a system-wide logical name or just has the physical device name be<strong>for</strong>e the res<strong>to</strong>re request is<br />

executed. If you do not want <strong>to</strong> use the logical name, then specify the physical device name followed<br />

by the direc<strong>to</strong>ry path as the destination <strong>for</strong> the res<strong>to</strong>re request.<br />

ABS allows you <strong>to</strong> enter a list of drives that can be used by save and res<strong>to</strong>re operations <strong>to</strong> and<br />

from this archive. This should be used only <strong>to</strong> restrict the drives that would normally be available<br />

<strong>for</strong> these operations <strong>for</strong> some reason. Normally, you can let ABS select drives <strong>for</strong> all operations<br />

based on media type and location, and so you do not need <strong>to</strong> specify the drives in the<br />

archive. If you do specify drives, be aware that these drives apply <strong>to</strong> res<strong>to</strong>res as well as saves.<br />

Drives are only applicable <strong>to</strong> an archive type of TAPE.<br />

When the drive list is specified in the archive class, the drive is allocated by ABS/MDMS <strong>for</strong><br />

operation as below:<br />

1. Volume-set is not present in the archive class<br />

ABS will allocate the first available drive and continues <strong>to</strong> select a volume matching the<br />

selection criteria. If all the drives in drive list are not free then ABS will Indefinitely loop <strong>for</strong><br />

allocating the drives and wait <strong>for</strong> drive <strong>to</strong> be available.<br />

2. When the volume set is present in the archive class and the required volume is present in:<br />

– Slot - then ABS selects the first available drive from the drive list.<br />

– Drive that is part of drive list in the archive class - In this condition the drive where the<br />

volume is currently present will be used <strong>for</strong> save operation.<br />

For example, if drive list consist of 2 drives A and B and if the required volume is present<br />

in B, then drive B will be used <strong>for</strong> the save/res<strong>to</strong>re operation even if drive A comes first in<br />

the drive list.<br />

3. Drive that is not a part of drive list - ABS will unload the volume from the drive and load the<br />

volume in first available drive in the drive list.<br />

Note<br />

The above allocation algorithm is applicable only when drive list is specified in the<br />

archive class.<br />

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

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

Saved successfully!

Ooh no, something went wrong!