This section in the User's Guide may help you: http://www-01.ibm.com/support/knowledgecenter/SSZHVN_7.1.3/erp.hana/c_dperp_saphana_cfg_scaleout.html
It is best if the /opt file system (more specifically the dsm.sys file) does not fail over. That way, each host uses its own TSM node name/password for authentication. Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 11/10/2015 05:32:31 AM: > From: Andrew Collyer <andrew.coll...@yorkshirewater.co.uk> > To: ADSM-L@VM.MARIST.EDU > Date: 11/10/2015 05:34 AM > Subject: Password synchronisation of TDPERP for SAP HANA on a scale- > out cluster > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > Hi all > > I?m hoping for some advice on the configuration of TDPERP for HANA. > > In our environment we have two HANA Linux servers running a single > instance in an Active/Passive setup. TDP is configured on both servers > and I have a single TDP node defined on a single TSM server. I am using a > proxy node within the TDP configuration of the two servers to handle the > communication back to the single TDP node on the TSM Server. > > The problem I have is that when a HANA failover occurs, the TDP config on > the newly active server does not have the correct TDP node password as it > isn?t maintained or synchronised with that on the original server. I > looked at copying the init<SID>.bki file but this seems to be encrypted > with something unique to the server. > > Is there a mechanism for synchronising the TDP node password between > servers on Linux? Any recommendations or work-arounds? > > Thanks in advance. > > Andrew > > Technical Architect ? Infrastructure > Yorkshire Water >