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 NetBackup for SAP backups
The brbackup command initiates the backup for SAP on Oracle databases. The brbackup command calls the NetBackup for SAP agent (backint) with appropriate options and gives a list of files for backup. Backups can be either successful or unsuccessful.
The results are as follows:
For a successful backup:
For each file that is backed up successfully, backint sends the following message to brbackup:
#SAVED BID filename
For each SAVED ... message that brbackup receives, brbackup writes the following information to its log file:
UNIX or Linux:
#FILE..... /home1/orasap/inp/file1
#SAVED.... VXF1134574401
Windows:
#FILE..... C:\oracle\SUD\sapdata1\file1.dbf
#SAVED.... VXF1134574401
For an unsuccessful backup:
For each file that is not backed up successfully, backint sends the following message to brbackup:
#ERROR filename
For each ERROR ... message that brbackup receives, brbackup writes the following message to its log file:
UNIX or Linux:
BR0233E Backup utility has reported an error while saving
file /home/orasap/inp/filename
Windows:
BR0233E Backup utility has reported an error while saving
file C:\oracle\SUD\sapdata1\file1.dbf
A backup can fail for several reasons that are unrelated to NetBackup operations:
The tape library ran out of tapes
A network connection problem occurred
The user killed the backup but wants to restart it sometime later
For situations like these, NetBackup for SAP saves the partial image for the files that have been already backed up.
Catalog entries in the NetBackup catalog are also saved. It returns the following messages:
#SUCCESS BID filename - For the files that were backed up
#ERROR filename - For the files that were not backed up
If a backup has terminated because of any problems that are not related to NetBackup, you do not have to repeat a complete backup again. Use the brbackup command and the -f logfile parameter. The brbackup command automatically determines the files that still need to be backed up. The next section describes how to use the -f parameter to restart a backup.