CATSEARCH restore jobs let you restore data when a catalog is available. CA VM:Backup searches backup catalogs for information about backed-up data to restore. CA VM:Backup uses the catalogs to determine the following information:
CATSEARCH jobs specify a time period. The default time period is 01/01/1942 00:00 (start date and time) through the current date and time (end date and time). You can specify a different time period.
For domain restores, CA VM:Backup uses the time period to determine which version of the domain to restore. If the version selected is from an incremental backup, CA VM:Backup uses all previous incremental backups and the full backup on which they are based to perform the restore, even if these backups were performed before the start date of the time period. In other words, for domain restores, the start date of the time period does not act as a cutoff date specifying which backups the job can use. CA VM:Backup will go back as far as the full backup even if it was performed before the start date of the time period.
For example, suppose you want to restore a file space as it existed on 10/08/04. You specified a range of 10/07/04 00:00 to 10/08/04 23:59. This range includes two incremental backups, but not the full backup, which was taken on 10/06/04. To restore the file space, CA VM:Backup will go back to the full, even though it exists outside the range.
Note: TPI domain restores search for domains, not individual files. If you submit a domain restore with an exception file that specifies particular files to be restored, and those files are not present in the domain that the job found, CA VM:Backup does not extend the search to look for those files, and the files are not restored.
Because of the way CA VM:Backup stores file pool information in the catalogs, specify a start date when restoring:
The start date will prevent CA VM:Backup from restoring more data than you intended. For example, suppose you want to restore a file pool. Two weeks ago (12/01/04) you deleted many file spaces from it and you do not want CA VM:Backup to restore them. To make sure CA VM:Backup does not restore the deleted file spaces, specify a start date that is later than 12/01/04, but early enough to contain the data you want to restore. If you do not specify a start date, CA VM:Backup uses the default start date (01/01/1942) and continues searching for and restoring file spaces back to that date.
After CA VM:Backup has determined which tapes to mount, it mounts the tapes and performs the restore. The order in which CA VM:Backup mounts the tapes depends on which of the CLEAR, NEWFILE, or REPLACE options is in effect. With NEWFILE, CA VM:Backup works from the most recent tape back to the full backup. With CLEAR and REPLACE, CA VM:Backup works from the oldest tape forward to the most recent.
When a catalog contains file-level detail, CA VM:Backup knows where to find the data on the tapes and can restore it quickly. When a catalog does not contain file-level information, either because it was created with domain-level detail or because it was condensed, CA VM:Backup mounts backup tapes and searches them for the data. CA VM:Backup restores the data when it finds it on the tapes; the operator need mount the tapes only once.
End user restores of BFS files are always VOLSER jobs. Restores of SFS and BFS data through the Submit Special SFS/BFS Restores screen are always CATSEARCH restore jobs. (If catalogs are not available, you can restore SFS and BFS data through VOLSEARCH restore job template files created using TPI.)
When a CATSEARCH restore job starts, CA VM:Backup:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|