HP Archive Backup System for OpenVMS Guide to Operations

2.2.6 Schedules
2.3 ABS Catalogs
Overview
2.3 ABS Catalogs
You can use a variety of ways of scheduling your save and restore requests, including two methods
provided by MDMS, or by the use of a third-party scheduler product (see Section 2.7). The
schedule object defines on what days and times a save or restore request is run. If you use
MDMS scheduling, these schedule objects are executed at the appropriate times and the associated
save and restore requests are invoked. If you use a third-party scheduler, the schedule
objects are still created, but they do not invoke the associated save or restore requests - that is
done by the third-party scheduler. The schedule object is created when you create the associated
save or restore request.
For most save and restore requests, you can define a frequency of operation, which together with
a base date determine the schedule attributes automatically. However, if you use internal MDMS
scheduling, you can specify a custom schedule, and set attributes for scheduling including the
following
• The days of the week you wish a request to run
• The dates of the month you wish a request to run
• The months of the year you wish a request to run
• The times of the day you wish a request to run - a request can run up to 100 times per day
• Specific dates in the next 10 years you wish a request to run, that otherwise would not be run
according to the other selection criteria
• Specific dates in the next 10 years you wish the request not to run, that otherwise would be
run according to the other selection criteria.
• Relate one schedule to another, so that its associated save or restore request runs after the
related save or restore request.
If you use a third-party scheduler, you can specify non-standard frequencies by using an explicit
frequency and interval that is passed to the scheduler, or you can use the scheduler interface
directly to manipulate the frequency of the request.
An ABS catalog consists of a catalog object and the catalog files. The information contained in
an ABS catalog object includes:
• The type of catalog (FILES, DISKS, VOLUME_SETS)
• Whether or not to use an intermediate staging file
• Who is allowed to access the catalog (for data safety)
• Who is allowed write data to and read data from the catalog (ensures data safety)
The ABS catalog files contain history information about save requests and can be assigned to
one or more archives. Each time a save request is initiated through a particular archive, the save
request history is recorded in an ABS catalog associated with the archive.
The information contained in an ABS catalog includes:
• The name of the data that was saved
• The type of data that was saved (OpenVMS Files, Oracle Rdb Database, Oracle Rdb Storage
Area, UNIX Files, Microsoft Windows Files, Oracle Database)
• The date and time the data was saved
• The save set name where the data is located
Overview 2–5