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
Recovery of SAP HANA database from tape storage fails
Recovery of SAP HANA database from tape storage fails to complete successfully as the restore jobs hang indefinitely. This failure is specifically seen during the logs restore phase.
By default, SAP HANA does not read all the pipes that it has opened during recovery. As NetBackup processes the pipes randomly, it is possible that the pipe where NetBackup tries to write is not open. This situation creates a deadlock situation and hence the jobs are stalled in the Activity Monitor.
To streamline the read and write operations on the pipe, set the following parameter in the global.ini
file:
In HANA Studio, double-click on instance tab.
1 as the max_recovery_backint_channels value (by default, this value is 64).
-> -> -> -> enterThis setting ensures that only a single request is sent to NetBackup. Hence only a single pipe is open for reading and NetBackup writes on that pipe only.
Note:
This issue is not seen in case of disk recovery. Hence no change is required for max_recovery_backint_channels in case of disk recovery.