You can significantly reduce the amount of space required to store catalogs on the catalog minidisk by the following methods:
CA VM:Backup removes all file, alias, track, and block information from file-level catalogs and retains a general entry for the minidisks, file spaces, and directories backed up. CA VM:Backup then condenses any catalogs created by incremental backups that are based on catalogs it has condensed.
CA VM:Backup erases catalogs from the catalog minidisk and removes any references to the erased catalogs from the catalog index files. CA VM:Backup then discards any catalogs created by incremental backups that are based on catalogs it has discarded.
You can condense a specific catalog using the CONDENSE command. You can discard a specific catalog using the DISCARD command. Or you can run an AUTOCAT job to condense or discard multiple catalogs based on auto-condense and auto-discard dates. Each backup job that creates a catalog records an auto-condense date and an auto-discard date in that catalog. For example, a backup job might record that CA VM:Backup should condense its catalog after 15 days and discard it after 30 days. When you run an AUTOCAT job, CA VM:Backup searches the catalog minidisk for catalogs whose auto-condense or auto-discard date has passed and condenses or discards those catalogs.
You can manually submit AUTOCAT jobs using the SUBMIT command, or you can configure CA VM:Backup to automatically submit an AUTOCAT job at a certain time each day using the AUTOCAT configuration file record. AUTOCAT jobs are based on TPI job template files. CA provides a sample AUTOCAT job template file called AUTOCAT TEMPDIST on your distribution tape. You can change auto-condense or auto-discard dates for catalogs using the UPDATE command or CA VM:Backup system administrator screens.
Notes:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|