HP Archive Backup System for OpenVMS Guide to Operations

Saving and Restoring Data
3.2 Catalogs
3.2.8.3 Catalog Cleanup
To clean expired entries from the catalog, there is a process that runs in the ABS$node batch
queue called ABS_CLEAN_CATLG_node. This process is scheduled to run once a day at 12:30
pm. The scheduled time is set in the
ABS$SYSTEM:ABS$START_CATALOG_CLEANUP.COM procedure. You may modify the
start time for the job or change the frequency of the job. If you do not have lot of expired entries
daily, you may want to run the job less frequently.
The log file generated by this cleanup process is called
ABS$LOG:ABS$CATALOG_CLEANUP.LOG. A lot of information about how many records
were read from the catalog, how many were deleted, and any errors are kept in this log. Most
errors seen should be reported to HP.
The catalog cleanup process cleans up all the catalogs when executed. We can also nominate the
catalogs that need to be cleaned up. Also, we can specify the interval in which this cleanup process
needs to run. This would be helpful:
1. If the cleanup process of all the catalogs takes a long time affecting the other daily jobs.
2. Cleanup of all the catalogs need not done always.
To nominate catalogs for cleanup:
– Stop the catalog cleanup process.
– Submit the cleanup COM file with the parameters as mentioned below:
$ @ABS$SYSTEM:ABS$START_CATALOG_CLEANUP catalog_names interval
catalog_names - Space delimited catalog names. Default: All Catalogs
Interval - "+n-"(n denoting the frequency at which the catalogs need to
be cleaned). Default: Every Day
Example:
$ @ABS$SYSTEM:ABS$START_CATALOG_CLEANUP "CATLG1 CATLG2 CATLG3" "+2-"
This command would nominate CATLG1,CATLG2,CATLG3 catalogs for cleanup and the
cleanup runs with the frequency of 2 days. i.e if submitted on 01-Nov-2001, then cleanup runs
on 03-Nov-2001 at 12:30, 05-Nov-2001 at 12:30 and so on.
Note
The cleanup of the VAOE file can be performed only after defining the
ABS_CATALOG_VAOE_CLEANUP logical System-wide.
$ DEFINE/SYSTEM ABS_CATALOG_VAOE_CLEANUP 1
3.2.8.4 Staging Catalog
With staging enabled for a catalog ABS writes the catalog entries to a sequential file during a
save operation. The save operation at the end creates a command procedure and executes it in a
separate process. This unpack process moves all entries from the staging catalog to the final catalog.
If all entries have been moved successfully the command procedure is deleted. If the
unpack process failed for some reason you can run the command procedure manually. To do this,
find the location and name of the command procedure in the logfile of the save request. Then
execute the command procedure on the node where the save request was running.
3-10 Saving and Restoring Data