If you indicate that CA VM:Backup should not wait for linked users to detach minidisks when it cannot obtain a link, CA VM:Backup skips restoring that particular backup of that minidisk and records this information in the summary section of the restore job detail report and in the keyword data report if the job creates one.
For example, you have both a full and an incremental CMS backup of a minidisk. You submit a restore job to restore the minidisk with data from both backup jobs. If CA VM:Backup tries to link to the target minidisk to restore the full backup data and cannot obtain write access, CA VM:Backup records a message in the restore job summary report, and the keyword data report if the job creates one, indicating this. Processing does not stop for this minidisk; CA VM:Backup tries to link to this minidisk again to restore data from the incremental backup. If CA VM:Backup obtains write access on this attempt, it restores data from the incremental backup.
Note: In this situation, CA VM:Backup was unable to restore requested data from the full backup, but was successful in restoring data from the incremental backup. Therefore, the restored version of the minidisk may be different from what was requested.
If CA VM:Backup does not obtain write access on this attempt, it records a second error message in the summary section of the restore job detail report and considers processing complete.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|