NetBackup™ for SAP Administrator's Guide
- Introduction to NetBackup for SAP
- About NetBackup for SAP
- Features of NetBackup for SAP
- Technical overview of NetBackup for SAP
- Sequence of operation for NetBackup for SAP
- Using NetBackup for SAP on Oracle databases without RMAN
- Using NetBackup for SAP on Oracle databases with RMAN
- SAP tools overview
- NetBackup for SAP on MaxDB databases
- Introduction to NetBackup SAP HANA
- Installing NetBackup for SAP
- Planning the installation of NetBackup for SAP
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- SAP server software requirements
- Requirements for using NetBackup for SAP MaxDB, SAP Oracle, and SAP HANA in a NetBackup cluster
- Configuration and licensing requirements for NetBackup for SAP with Snapshot Client
- License for NetBackup for SAP
- Copying the SAP binary file (Windows Oracle databases without RMAN only)
- Linking NetBackup for SAP with backint (UNIX or Linux Oracle databases without RMAN only)
- Linking the Oracle instances with the SBT library (UNIX or Linux Oracle databases with RMAN only)
- Installing NetBackup for SAP HANA
- Configuring NetBackup for SAP
- About configuring NetBackup for SAP
- About configuring a backup policy for SAP
- Adding a NetBackup for SAP policy
- About policy attributes
- NetBackup for SAP backup types
- Configure an application backup schedule
- Example application backup schedule
- Configure automatic backup schedules
- Example automatic backup schedule
- Schedule properties
- Add clients to a policy
- Adding NetBackup for SAP scripts to the backup selections list
- Rules for NetBackup for SAP scripts
- NetBackup for SAP backup scripts
- Configuring the logon account for the NetBackup Client Service for NetBackup for SAP
- About SAP configuration files
- Relationships between SAP database configuration files
- Modifying the initSID.utl file for NetBackup for SAP
- Example NetBackup for SAP initSID.utl file
- Modifying the initSID.sap file (NetBackup for SAP Oracle databases only)
- Example initSID.sap file (NetBackup for SAP on Oracle databases only)
- Modifying the bsi.env file (NetBackup for SAP on MaxDB databases)
- Backing up files mounted with LOFS with NetBackup for SAP (UNIX or Linux)
- About permissions for NetBackup for SAP log files (UNIX)
- Reviewing the auto-discovered mappings
- Configuring the Maximum jobs per client
- Perform a manual backup
- Testing multiple concurrent backup jobs for NetBackup for SAP for Oracle (without RMAN)
- Configuring NetBackup for SAP HANA
- Performing backups and restores of SAP
- Using NetBackup for SAP to perform a backup
- Using BRTools to start an SAP backup (for Oracle database only)
- Performing an SAP archive
- Performing SAP restores using the SAPDBA utility (SAP on Oracle databases only)
- Redirecting a restore to a different client (SAP on Oracle databases only)
- SAP redirected restore sample environment (UNIX)
- Disaster recovery using BRRECOVER
- Restarting failed NetBackup for SAP backups and restores
- Performing backups and restores of SAP HANA
- NetBackup for SAP with Snapshot Client
- NetBackup for SAP with Snapshot Client overview
- Using NetBackup for SAP with Snapshot Client to back up large databases
- How the NetBackup for SAP Snapshot Client works
- Configuration requirements for snapshot backups with NetBackup for SAP
- About configuring Snapshot Client with NetBackup for SAP
- Configuring a snapshot policy for NetBackup for SAP
- About NetBackup for SAP backup types
- Prerequisites for instant recovery backups (UNIX or Linux)
- Configuring a snapshot policy with Instant Recovery for NetBackup for SAP
- Additional configuration required for NetBackup for SAP with Network Attached Storage (NAS) on UNIX or Linux
- Configuring a NAS snapshot policy for NetBackup for SAP on UNIX/Linux
- About configuring NetBackup for SAP block-level incremental backups on UNIX
- How BLI works with NetBackup for SAP (UNIX)
- About Nodata Storage Checkpoint and NetBackup for SAP
- About Fulldata Storage Checkpoint and NetBackup for SAP
- Storage Checkpoint configuration on the NetBackup for SAP client
- Configuration requirements for BLI backups with NetBackup for SAP
- Configuring policies for BLI backups with NetBackup for SAP
- About restoring individual files from a NetBackup for SAP snapshot backup
- About NetBackup for SAP restores of volumes and file systems using snapshot rollback
- About NetBackup for SAP sample backup scripts (UNIX or Linux)
- About NetBackup for SAP sample backup scripts (Windows)
- Mixing RMAN stream and RMAN proxy NetBackup for SAP backups
- Performing user-directed snapshot backups with NetBackup for SAP
- NetBackup for SAP on MaxDB databases
- Troubleshooting NetBackup for SAP and SAP HANA
- About troubleshooting NetBackup for SAP
- NetBackup debug logs and reports
- Enabling the debug logs for a NetBackup for SAP client automatically (Windows)
- Enabling the debug logs manually (Windows) (NetBackup for SAP)
- Enabling the debug logs manually (UNIX)
- About the bphdb directory on the Windows database client
- About the bphdb directory on the UNIX database client
- About the backint directory on the UNIX database client
- About the backint directory on the Windows database client
- Setting the debug level on a Windows client
- Setting the debug level on a UNIX client
- About NetBackup server reports
- sapdba logs and messages (Oracle-based SAP environments only)
- NetBackup SAP Oracle backup jobs fail with error 90
- NetBackup for SAP Oracle backup fails
- Minimizing time-out failures on large database restores
- About troubleshooting NetBackup for SAP HANA
- Disaster recovery of an SAP Hana database
- 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
- About parameters used in initSID.utl
- initSID.utl parameter summary
- backup_stream_buffersize <size>
- client <client_name>
- custom_sort_file <file_path>
- drives <number_of_drives>
- inquiry_query_period <months>
- master_time_offset <minutes> (UNIX or Linux)
- multistream_restore
- policy <policy_name>
- policy2 <policy_name>
- restore_stream_buffersize <size>
- retry_backup <number_of_retries>
- schedule <schedule_name>
- schedule2 <schedule_name>
- server <server_name>
- sort_backup_type <value>
- sort_restore_type <value>
- switch_list <control_file_path>
- switch_log <control_file_path>
- switch_sem <control_file_path>
- Appendix H. Configuring split mirror backups
- About configuring split mirror backups
- Local-host snapshot method: nbu_snap (Solaris SPARC platform only)
- Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows)
- Local-host snapshot method: VxFS_Checkpoint (UNIX or Linux)
- Off-host alternate client, FlashSnap method
- Off-host alternate client, VVR method (Solaris SPARC, HP-UX)
- Hardware array-based snapshot method: Hitachi Shadow Image, EMC TimeFinder, HP Business Copy (UNIX or Linux)
- Appendix I. Register authorized locations
About configuring NetBackup for SAP block-level incremental backups on UNIX
If only a small portion of a database changes on a daily basis, full database backups are costly in terms of time and media. The Block-Level Incremental (BLI) Backup interface extends the capabilities of NetBackup to back up only the file system blocks that contain changed data blocks.
A database BLI backup is done at the file system block level, which means only changed file blocks are backed up. Unchanged blocks within the files are not backed up. The VxFS Storage Checkpoint facility tracks changed blocks in real time. Accordingly, a BLI backup does not need to search the entire volume for the modified blocks at backup time. BLI backup saves time, decreases the amount of backup media that is required, and significantly reduces CPU and network overhead during backups. In addition, BLI backup allows more frequent backups, so backup images are more up to date.
BLI backup is particularly useful for any large databases that are sized in terms of hundreds of gigabytes or terabytes. Most traditional methods for database backup require that any change in the database - no matter how small - requires that the entire database is backed up. With BLI backup, only modified blocks (or file) need to be backed up.
See Configuring policies for BLI backups with NetBackup for SAP.