In this lab, we will show you how to put a cluster node on standby so that all cluster services running on the cluster node are automatically migrated to the secondary node.
Connect to Bastion Host and check the Dashboard of HAWK web (refer to Lab02)
Connect to sechana and check the cluster and HSR status.
Connec to EC2 Instance Console
Select HANA-HDB-Secondary instance, click Action, and click Connect.
Select Session Manager and click Connect. Connect to sechana instance through Session Manager
Check the cluster status.
sudo su -
crm_mon -rfn1
Check SAP HANA System Replication (HSR) status.
sudo su -
SAPHanaSR-showAttr
Run the command below to put Node2 (sechana) into standby mode. (Use root user)
sudo su -
crm node standby sechana
The cluster starts prihana SAP HANA database, and takeover from the sechana. If the system replication synchronization was performed. Wait for the prihana to become brand new Primary.
Connect to Bastion Host and check the Dashboard of HAWK web (refer to Lab02)
Check the cluster status until the resource is migrated from Node2 (sechana) to Node1 (prihana).
sudo su -
crm_mon -rfn1
Set Cluster Node2 (sechana) online (using root user)
sudo su -
crm node online sechana
Cluster status is checked until Cluster Node2 (sechana) is online.
sudo su -
crm_mon -rfn1
Cleans up the SAPHana resource status.
crm resource cleanup rsc_SAPHana_HDB_HDB00
© 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.