Symptom
- Finished installation of a SAP HANA Scale-Out on a TDI approach.
- Storage Connector API used during the SAP HANA installation is - fcClientLVMMpath.py(i.e. ha_provider = hdb_ha.fcClientLVMMpath in global.ini).
The Storage API Guide from the SAP Note:1900823, mentions about a reservation key.
============================================
Further it allows automatic registration of reservation keys in case new device paths are added to a LUN or
become active again. However, for this to work you have to add the reservation key used by SAP HANA for
each host to /etc/multipath.conf .
You can run ‘python $DIR_INSTANCE/exe/python_support/hdb_ha/hdbmount.py --reservationKey’ as sidadm on each host to get the corresponding reservation keys.
============================================ - In case of the fail-over, how does the reservation key get transferred to the new master indexserver node?
Read more...
Environment
- SAP HANA, platform edition 2.0
Scale-Out System(ex, 1 Master + 5 Workers + 1 Standby)
Product
SAP HANA, platform edition 2.0
Keywords
Reservation key, scaleout, scale-out, HANA , KBA , HAN-LM-INS-DB , Installation of HANA Database , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview