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 SAP
- NetBackup for SAP backup scripts
- About SAP configuration files
- Configuring NetBackup for SAP HANA
- Configuring the master server for NetBackup SAP HANA
- Configuring the NetBackup client
- Configuring the SAP HANA Agent
- 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
- Restarting NetBackup for SAP backups
- Restarting SAP database restores on Oracle
- 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
- Using NetBackup for SAP on a MaxDB database to perform backups and restores
- 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
Reviewing the auto-discovered mappings in Host Management
In certain scenarios, a NetBackup host shares a particular name with other hosts or has a name that is associated with a cluster. To successfully perform backups and restores with NetBackup for SAP, you must approve each valid Auto-Discovered Mapping that NetBackup discovers in your environment. These mappings appear in the Host Management properties on the master server. You can also use the nbhostmgmt command to manage the mappings. See the NetBackup Administrator's Guide, Volume I for more details on Host Management properties.
Examples of the configurations that have multiple host names include:
A host is associated with its fully qualified domain name (FQDN) and its short name or its IP address.
If the SAP server is clustered, the host is associated with its node name and the virtual name of the cluster.
In a SAP cluster environment, you must map the node names to the virtual name of the cluster if the following apply:
If the backup policy includes the cluster name (or virtual name)
This mapping is not required for SAP HANA. That type of policy includes the node names in the cluster and not the virtual name of the cluster.
If the NetBackup client is installed on more than one node in the cluster
If the NetBackup Client is only installed on one node, then no mapping is necessary.
This procedure only applies to SAP, not to SAP HANA.
To approve the auto-discovered mappings for a cluster
- In the NetBackup Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval tab.
The list displays the hosts in your environment and the mappings or additional host names that NetBackup discovered for those hosts. A host has one entry for each mapping or name that is associated with it.
For example, for a cluster with hosts
client02.lab04.com, you may see the following entries:
- If a mapping is valid, right-click on a host entry and click Approve.
For example, if the following mappings are valid for
client01.lab04.com, then you approve them.
Valid name for
The short name of the client
The virtual name of the cluster
The FQDN of the virtual name of the cluster
- When you finish approving the valid mappings for the hosts, click on the Hosts tab at the bottom of the Hosts pane.
client02.lab04.com, you see Mapped Host Names/IP Addresses that are similar to the following:
Mapped Host Names/IP Addresses
client01.lab04.com, client01, clustername, clustername.lab04.com
client02.lab04.com, client02, clustername, clustername.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the node names in the cluster to which you want to map that virtual name.
Table: Example mapped host names for a SAP cluster environment
Cluster with two nodes
Physical name of Node 1
Virtual name of SAP server
Physical name of Node 2
Virtual name of SAP server