Veritas NetBackup™ for SAP Administrator's Guide
- Introduction to NetBackup for SAP
- Introduction to NetBackup SAP HANA
- Installing NetBackup for SAP
- Installing NetBackup for SAP HANA
- Configuring NetBackup for SAP
- About configuring a backup policy for an SAP database
- NetBackup for SAP backup scripts
- About SAP configuration files
- Configuring NetBackup for SAP HANA
- Performing backups and restores of SAP
- Using BRTools to start an SAP backup (for Oracle database only)
- Performing an SAP archive
- Restarting failed NetBackup for SAP backups and restores
- Performing backups and restores of SAP HANA
- NetBackup for SAP with Snapshot Client
- How the NetBackup for SAP Snapshot Client works
- About configuring Snapshot Client with NetBackup for SAP
- About configuring NetBackup for SAP block-level incremental backups on UNIX
- Configuring policies for BLI backups with NetBackup for SAP
- About NetBackup for SAP restores of volumes and file systems using snapshot rollback
- NetBackup for SAP on MaxDB databases
- Troubleshooting NetBackup for SAP and SAP HANA
- NetBackup debug logs and reports
- sapdba logs and messages (Oracle-based SAP environments only)
- About troubleshooting NetBackup for SAP HANA
- Appendix A. backint command line interface
- Appendix B. Input and output files for SAP HANA
- Appendix C. backint -i in_file contents
- Appendix D. backint -o out_file contents
- Appendix E. NetBackup for SAP environment variables for backint
- Appendix F. NetBackup for SAP configuration or bp.conf file settings
- Appendix G. Parameters used in initSID.utl
- sort_backup_type <value>
- sort_restore_type <value>
- Appendix H. Configuring split mirror backups
- Appendix I. Register authorized locations
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.