Task 01. Migrate Cluster

Task 01 shows how to perform a manual migration from SAP HANA running on the master node to the secondary (standby) node using the crm CLI. Before starting this lab, you should first verify that all services in the cluster are running normally without errors.

Architecture

image02

Migrating HANA primary

  1. Lab 02. Task 03. Execute HAWK (High Availability Web Konsole) to check the cluster status through Web.

  2. Execute Lab 03. Task 01. Validation of Cluster to check the cluster status through CLI.

  3. After logging in to the Management Console to migrate the Overlay IP resource, connect to EC2 Instance Console

  4. Select HANA-HDB-Primary instance, click Action, and click Connect. image01-01

  5. Select Session Manager and click Connect. Connect to prihana instance through Session Manager. image01-02

  6. On Node1 (prihana), run the command below to migrate the Overray IP resource res_AWS_IP to Node2 (sechana).

    sudo su -
crm resource migrate res_AWS_IP force

Since you used the “migrate” command, the cluster stops the RA of the Primary Node (prihana) in its current state and promotes the Secondary Node to “Master”. Primary should not be migrated if system clone is in INSYNC (SFAIL) state. Wait for the Secondary Node to become the new Primary.

  1. Connect to sechana and check the cluster and HSR status.

  2. Connect to EC2 Instance Console

  3. Select HANA-HDB-Secondary instance, click Action, and click Connect. image01-08

  4. Select Session Manager and click Connect. Connect to sechana instance through Session Manager image01-02

  5. Check the cluster status.

    • crm_mon is a command that provides the current state of the cluster (using root user).
    • Execute the command below to check if sechana is in Master status.
    sudo su -
crm_mon -rfn1

    image01-09

  6. Check SAP HANA System Replication (HSR) status.

    • Use SAPHanaSR-showAttr to confirm that the prihana node is SOK. (Use root user)
    sudo su -
SAPHanaSR-showAttr

    image01-10

  7. Connect to Bastion Host and check the Dashboard of HAWK web. (Refer to Lab02)

    • You can see that Overlay IP Resource has been moved to sechana. image01-12

  8. On Secondary Node (sechana), disable resource migration so that the cluster can start on Primary Node (prihana).

    sudo su -
crm resource unmigrate res_AWS_IP

© 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.