Symptom
You are looking for configuration recommendations for
Symantec NetBackup for SAP HANA, or you are encountering issues when
trying to backup or restore SAP HANA using the backing interface with
Symantec NetBackup.
Other Terms
Backup, Recovery, NetBackup, Symantec, Backint, SAP HANA
Reason and Prerequisites
You are using a SAP-certified solution of Symantec
NetBackup (versions 7.5 and 7.6) and a SAP HANA database (at least
revision 45).
Solution
The following documents give recommendations on how to configure
Symantec NetBackup for SAP HANA, or describe common issues with Symantec
NetBackup and how to resolve them.
Configuration Recommendations:
For Symantec NetBackup and SAP HANA version dependencies, please refer to the NetBackup 7.x Database Agent Compatibility List, available at http://www.symantec.com/docs/TECH126904.
Configuration Recommendations:
- Please make sure that the NetBackup for SAP HANA database agent has been installed correctly. The NetBackup for SAP 7.5.0.6 Administrator's Guide is available at http://www.symantec.com/docs/DOC5176. The NetBackup for SAP 7.6 Administrator's Guide is available at http://www.symantec.com/docs/DOC6482. Both guides include the SAP HANA specific installation procedures.
- Increase the Client Read Timeout in NetBackup to a large value. If
the Client Read Timeout is set too low, the SAP HANA restore job may
fail with error code 2850.
See Symantec TechNote TECH215225, available at http://www.symantec.com/docs/TECH215225 - If restoring from tape, set the parameter
MAX_RECOVERY_BACKINT_CHANNELS from the default value of '64' to a value
of '1' in SAP HANA Studio. If this parameter is not set accordingly,
sometimes a log restore from tape may hang until cancelled or eventually
timeout and fail.
See Symantec TechNote TECH211556, available at http://www.symantec.com/docs/TECH211556 - Tape backups on a multi-node or single-node SAP HANA appliance may
fail. Change the Client connect timeout and Client read timeout to 3000
seconds or more.
See Symantec KB article HOWTO88624, available at http://www.symantec.com/docs/HOWTO88624 - For scheduling SAP HANA backups from NetBackup please refer to Symantec TechNote TECH209343, available at http://www.symantec.com/docs/TECH209343
- Data recovery fails when the node_names.txt file is missing in
NetBackup SAP HANA at /usr/openv/netbackup/ext/db_ext/sap and if data
recovery is initiated from the SAP HANA Studio.
See Symantec TechNote TECH215391, available at http://www.symantec.com/docs/TECH215391 - If the library libelf.so.0 file is missing on the SAP HANA appliance
(known for IBM and HITACHI SAP HANA appliances), SAP HANA backup fails
with exit code 127.
See SAP Note 1978901 or Symantec TechNote TECH208377, available at http://www.symantec.com/docs/TECH208377 - Though backup is working, recovery fails in SAP HANA studio with "No
data backups found" (#NOTFOUND in backint.log) due to wrong hostnames
in node_names.txt.
See Symantec KB article DOC7480, available at http://www.symantec.com/docs/DOC7480 - An SAP HANA backup fails almost immediately if the initSAP.utl file
has not been configured correctly ("ERROR: switch_list missing from
parameter file")
See Symantec TechNote TECH216653, available at http://www.symantec.com/docs/TECH216653
For Symantec NetBackup and SAP HANA version dependencies, please refer to the NetBackup 7.x Database Agent Compatibility List, available at http://www.symantec.com/docs/TECH126904.
Header Data
Released On | 25.06.2014 14:25:35 |
Release Status | Released for Customer |
Component | BC-OP-LNX-VTS Veritas Products on Linux |
Priority | Recommendations / Additional Info |
Category | Help for error analysis |
No comments:
Post a Comment