No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Huawei SAP HANA Appliance Two Node Installation Guide (RH5885H and RH8100 V3+Redhat) 08

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Registering the Secondary HANA Node with the Primary HANA Node

Registering the Secondary HANA Node with the Primary HANA Node

You must register the secondary HANA node (HW00002 in this example) with the primary HANA node for SAP HANA system replication.

Before the registration, ensure that the network port is normal, stop the HANA database on the secondary HANA node, configure system replication on the secondary HANA node, and then restart the HANA database to complete the database system replication registration.

The procedure is as follows:

  1. Log in to the secondary HANA node (HW00002 in this example) as the root user. Run the su - s00adm command to switch to the HANA database user s00adm (replace s00 with the lowercase of the actual database SID).
  2. Run the HDB stop command to stop the HANA database and wait till the database is stopped.

    The process is similar to the following:

    HW00002:~ # su - s00adm
    HW00002:/usr/sap/S00/HDB00> HDB stop
    Stopping instance using: /usr/sap/S00/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00 -function Stop 400
    12.10.2015 15:11:23
    Stop
    OK
    Waiting for stopped instance using: /usr/sap/S00/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00 -function WaitforStopped 600 2
    12.10.2015 15:11:23
    WaitforStopped
    OK
    hdbdaemon is stopped.

  3. (Applicable to Redhat7.2) If the DB version is HANA2.0, you should run the following commands.

    1. Run the following command on the secondary HANA node to backup files (replace <SID> with the actual database SID).

      cd /usr/sap/<SID>/SYS/global/security/rsecssfs/data/

      cp -rp SSFS_<SID>.DAT SSFS_<SID>.DAT.bak

      cd /usr/sap/<SID>/SYS/global/security/rsecssfs/key/

      cp -rp SSFS_<SID>.KEY SSFS_<SID>.KEY.bak

    2. Run the following command on the primary HANA node to copy files to secondary HANA node (replace <SID> with the actual database SID).

    scp -rp /usr/sap/<SID>/SYS/global/security/rsecssfs/data/SSFS_<SID>.DAT root@HW00002:/usr/sap/<SID>/SYS/global/security/rsecssfs/data/

    scp -rp /usr/sap/<SID>/SYS/global/security/rsecssfs/key/SSFS_<SID>.KEY root@HW00002:/usr/sap/<SID>/SYS/global/security/rsecssfs/key/

  4. Run the following command on the secondary HANA node to register the secondary HANA node with the primary HANA node (If the DB version is earlier than HANA SPS 11, uses "mode=sync" to replacement the "replicationMode=sync" in this command):

    hdbnsutil -sr_register --remoteHost=hw00001  --remoteInstance=00 --replicationMode=sync  --name=hw00002 --operationMode=logreplay

    Parameters in the command are described as follows:

    • remoteHost: indicates the host name of the primary HANA node. In this example, the value is HW00001 and must be changed to the actual host name.
    • name: indicates the host name of the secondary HANA node. In this example, the value is HW00002 and must be changed to the actual host name of the local host (secondary HANA node).
    • replicationMode: There are three options sync (hard disk synchronization), async (hard disk asynchronization), syncmem (memory synchronization). Generally, sync is selected by default. The options async and sysnmem can be selected based on customer requirements, but these options have data loss risks.
    • remoteInstance: indicates the instance number of the HANA database and must be changed to the instance number configured during HANA installation.
    • operationMode:
      • HANA1.0: There are two options. The default option is delta_datashipping (HANA database data is transmitted between the primary and secondary nodes periodically, and the secondary node database takeover is more time-consuming). Another option is logreplay (Primary node logs are processed or redone on the secondary node in real time, and the secondary node takeover is less time-consuming). The logreplay option is recommended.
      • HANA2.0: There are three options: delta_datashipping, logreplay and logreplay_readaccess. The default option is logreplay. Primary node logs are processed or redone on the secondary node in real time, and the secondary node takeover is less time-consuming. The logreplay option is recommended. delta_datashipping, HANA database data is transmitted between the primary and secondary nodes periodically, and the secondary node database takeover is more time-consuming. logreplay_readaccess, system replication uses an initial data shipping to initialize the secondary site. After that only log shipping is done and log buffers received by the secondary are replayed there. Savepoints are executed individually for each service and column table merges are executed on the secondary site. Furthermore, read only access via SQL is possible to the secondary system.

    The process is similar to the following:

    HW00002:/usr/sap/S00/HDB00> hdbnsutil -sr_register --remoteHost=HGY00002  --remoteInstance=00 --replicationMode=sync  --name=HGY00001 --operationMode=logreplay
    adding site ...
    checking for inactive nameserver ...
    nameserver HW00002:30001 not responding.
    collecting information ...
    registered at 192.168.100.100 (HW00001)
    updating local ini files ...
    done.
    HW00002:/usr/sap/S00/HDB00>

  5. Run the HDB start command to start the database.
  6. Run the hdbnsutil -sr_state command to check the database status. If the displayed status is sync and the two nodes can be found, the synchronization mode registration is successful.

    The process is similar to the following:

    HW00002:/usr/sap/S00/HDB00> HDB start
    StartService
    Impromptu CCC initialization by 'rscpCInit'.
    See SAP note 1266393.
    OK
    OK
    Starting instance using: /usr/sap/S00/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00 -function StartWait 2700 2
    12.10.2015 15:16:53
    Start
    OK
    12.10.2015 15:17:27
    StartWait
    OK
    HW00002:/usr/sap/S00/HDB00> hdbnsutil -sr_state
    checking for active or inactive nameserver ...
    System Replication State
    ~~~~~~~~~~~~~~~~~~~~~~~~
    mode: sync
    site id: 2
    site name: HW00002
    active primary site: 1
    re-setup replication: hdbnsutil -sr_register --name=HW00002 --mode=sync --remoteHost=HW00001 --remoteInstance=00
    Host Mappings:
    ~~~~~~~~~~~~~~
    HW00002 -> [HW00001] HW00001
    HW00002 -> [HW00002] HW00002
    primary masters:HW00001
    done.
    HW00002:/usr/sap/S00/HDB00>

Translation
Download
Updated: 2019-05-14

Document ID: EDOC1100019155

Views: 17941

Downloads: 94

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next