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
sort_backup_type size (default)
This value is the default for the sort_backup_type parameter.
If sort_backup_type size is specified, backint sorts the files by size before distributing them amongst the jobs based upon the drives that are specified in the initSID.utl file.
The number of drives that are specified does not have to equal the number of physical storage units. The number of drives correlates to the number of simultaneous jobs created by the NetBackup for SAP backint interface. For example, if you have 10 SAP files and three tape drives, you can specify 10 drives in the initSID.utl file. This value creates 10 jobs with one file for each bpbackup job. NetBackup handles all of the job scheduling. Initially, three jobs are active and the other seven jobs are queued.
Note:
Not applicable in MaxDB database environments or in any Oracle database environments that use RMAN.
For example, if three tape drives are specified, the files are divided evenly into three bpbackup jobs based on size. So, if there are 25 input files from SAP and three tape drives, then three bpbackup jobs run at the same time.
The following files are in each job, on UNIX or Linux:
Input file list from SAP (brbackup, sapdba):
/oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/EL30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s6 11812864 /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf /oracle/sap/saplog1/log_g2_m1/log2_m1.dbf /oracle/sap/saplog1/log_g3_m1/log3_m1.dbf /oracle/sap/saplog1/log_g4_m1/log4_m1.dbf /oracle/sap/dbs/cntrlSAP.dbf
Backup job 1:
size= 36708352: file /name=/oracle/sap/sapdata1/roll_1/roll.data1 size= 10493952: file name=/oracle/sap/sapdata1/temp_1/temp.data1 size= 5251072: file name=/oracle/sap/sapdata1/ddicd_1/ddicd.data1 size= 5251072: file name=/oracle/sap/sapdata1/el30ci_1/el30ci.data1 size= 5243392: file name=/oracle/sap/saplog1/log_g4_m1/log4_m1.dbf Total=62947840
Backup job 2:
251072: file name=/oracle/sap/sapdata2/btabi_1/btabi.data1 size= 5251072: file name=/oracle/sap/sapdata5/ddici_1/ddici.data1 size= 5251072: file name=/oracle/sap/sapdata6/es30cd_1/es30cd.data1 size= 5251072: file name=/oracle/sap/sapdata2/poold_1/poold.data1 size= 5251072: file name=/oracle/sap/sapdata3/stabd_1/stabd.data1 size= 5251072: file name=/oracle/sap/sapdata1/pooli_1/pooli.data1 size= 5251072: file name=/oracle/sap/sapdata2/user1i_1/user1i.data1 size= 5243392: file name=/oracle/sap/saplog1/log_g1_m1/log1_m1.dbf size= 231936: file name=/oracle/sap/dbs/cntrlSAP.dbf Total=57969664
Backup job 3:
size= 11812864: file name=/dev/rdsk/c0t4d0s6 size= 5251072: file name=/oracle/sap/sapdata2/clud_1/clud.data size= 5251072: file name=/oracle/sap/sapdata4/el30cd_1/EL30cd.data1 size= 5251072: file name=/oracle/sap/sapdata4/protd_1/protd.data1 size= 5251072: file name=/oracle/sap/sapdata2/sourced_1/sourced.data1 size= 5251072: file name=/oracle/sap/sapdata2/stabi_2/stabi.data2 size= 5251072: file name=/oracle/sap/sapdata4/user1d_1/user1d.data1 size= 5251072: file name=/oracle/sap/sapdata1/btabd_1/btabd.data1 size= 5243392: file name=/oracle/sap/saplog1/log_g2_m1/log2_m1.dbf size= 5243392: file name=/oracle/sap/saplog1/log_g3_m1/log3_m1.dbf Total=59057152
The following files are in each job, on Windows:
Input file list from SAP (brbackup, sapdba):
Backup job 1:
Backup job 2:
Backup job 3:
More Information