In a Scale Out landscape it is possible for any node to be a worker at any point in time. This requires that each node is able to access any backup images which have been created by another node. To inform the Netbackup configuration that images created by one node may need to be accessed by another node, a node_names.txt needs to be created.
- Create the file "node_names.txt" in "/usr/openv/netbackup/ext/db_ext/sap/" and place the hostname of all of the nodes in it:
- echo "`hostname -f`" >> /usr/openv/netbackup/ext/db_ext/sap/node_names.txt
- Copy this file to each node in the landscape (both worker and standby).
If Netbackup is aware of the clients using the fully qualified domain names, then the hostname may need the domain name added to each entry.
Check the CLIENT_NAME parameter in /usr/openv/netbackup/bp.conf for each node, this is the name which needs to be added to node_names.txt:
SERVER = nbu-sap.puredoes.local
CLIENT_NAME = rhana01.puredoes.local
CONNECT_OPTIONS = localhost 1 0 2
The node_names.txt file should be similar to the below:
rHANA01.puredoes.local
rHANA02.puredoes.local
rHANA03.puredoes.local
rHANA04.puredoes.local
- Identify the node on which the master nameserver is running:
- Logged in as the <sid>adm user execute the python script "landscapeHostConfiguration.py".
- Located in /usr/sap/<sid>/HDB<instance_number>/exe/python_support
python /usr/sap/RH1/HDB00/exe/python_support/landscapeHostConfiguration.pyThe following table will be returned: note the column for NameServer Actual Role and which host is marked as "master".
| Host | Host | Host | Failover | Remove | Storage | Storage | Failover | Failover | NameServer | NameServer | IndexServer | IndexServer | Host | Host | Worker | Worker | | | Active | Status | Status | Status | Config | Actual | Config | Actual | Config | Actual | Config | Actual | Config | Actual | Config | Actual | | | | | | | Partition | Partition | Group | Group | Role | Role | Role | Role | Roles | Roles | Groups | Groups | | ------- | ------ | ------ | -------- | ------ | --------- | --------- | -------- | -------- | ---------- | ---------- | ----------- | ----------- | ------ | ------ | ------- | ------- | | rhana01 | yes | ok | | | 1 | 1 | default | default | master 1 | master | worker | master | worker | worker | default | default | | rhana02 | yes | ok | | | 2 | 2 | default | default | master 2 | slave | worker | slave | worker | worker | default | default | | rhana03 | yes | ok | | | 3 | 3 | default | default | master 3 | slave | worker | slave | worker | worker | default | default | | rhana04 | yes | ok | | | 4 | 4 | default | default | slave | slave | worker | slave | worker | worker | default | default | overall host status: okOn the NamServer master host - create the soft link:
- Logged in as the <sid>adm user execute the python script "landscapeHostConfiguration.py".
- The Netbackup "hdbbackint_script" file location is typically /usr/openv/netbackup/bin/hdbbackint_script.
- The soft link needs to be created to /usr/sap/$SAPSYSTEMNAME/SYS/global/hdb/opt/.
- In some versions of SAP HANA the "opt" directory will need to be created before creating the soft link.
To create the soft link execute the following:
ln -s /usr/openv/netbackup/bin/hdbbackint_script /usr/sap/$SAPSYSTEMNAME/SYS/global/hdb/opt/hdbbackint