Restarting failed NetBackup for SAP backups and restores
A backup or a restore can fail or terminate because of system error or resource contention. For example, a backup can fail because of the following reasons: the tape library ran out of tapes, the storage unit ran out of space, or a network connection was lost. In the case of large environments with more than a terabyte of data, it might not be feasible to repeat the backup all over again.
If the policy is enabled for checkpoint restart, SAP tools can resume the backup from a point shortly before the failure. If enabled, the default checkpoint interval is 15 minutes unless adjusted on the backup policy's attributes tab. For a failed job, NetBackup retains partial image and catalog entries in the NetBackup catalog for the files that have been already backed up.
SAP tools can also restart a restore of just the files that were not previously restored. This ability is independent of the checkpoint restart option in the backup policy.
Caution:
Attempts to restart a backup or restore from the Activity Monitor will fail.
Note:
SAP tools use backint to restart failed backups and restores of Oracle databases.
Sap tools do not support the use of RMAN to restart failed backups and restores of Oracle databases. MaxDB also cannot restart failed backups or restores.