Skip to content

Commit 5449891

Browse files
authored
Merge pull request #116150 from rdeltcheva/rhel-hana-upd
Remove warning that fenced VM can take 15 minutes to restart
2 parents 536cafc + 1f1a366 commit 5449891

File tree

1 file changed

+22
-5
lines changed

1 file changed

+22
-5
lines changed

articles/virtual-machines/workloads/sap/sap-hana-high-availability-rhel.md

Lines changed: 22 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: virtual-machines-linux
1212
ms.topic: article
1313
ms.tgt_pltfrm: vm-linux
1414
ms.workload: infrastructure
15-
ms.date: 03/31/2020
15+
ms.date: 05/21/2020
1616
ms.author: radeltch
1717

1818
---
@@ -706,9 +706,6 @@ See [Red Hat Knowledgebase article 79523](https://access.redhat.com/solutions/79
706706
The virtual machine should now restart or stop depending on your cluster configuration.
707707
If you set the `stonith-action` setting to off, the virtual machine is stopped and the resources are migrated to the running virtual machine.
708708

709-
> [!NOTE]
710-
> It can take up to 15 minutes until the virtual machines is online again.
711-
712709
After you start the virtual machine again, the SAP HANA resource fails to start as secondary if you set `AUTOMATED_REGISTER="false"`. In this case, configure the HANA instance as secondary by executing this command:
713710

714711
<pre><code>su - <b>hn1</b>adm
@@ -779,9 +776,29 @@ Resource Group: g_ip_HN1_03
779776
vip_HN1_03 (ocf::heartbeat:IPaddr2): Started hn1-db-1
780777
</code></pre>
781778

779+
### Test a manual failover
780+
781+
Resource state before starting the test:
782+
783+
<pre><code>Clone Set: SAPHanaTopology_HN1_03-clone [SAPHanaTopology_HN1_03]
784+
Started: [ hn1-db-0 hn1-db-1 ]
785+
Master/Slave Set: SAPHana_HN1_03-master [SAPHana_HN1_03]
786+
Masters: [ hn1-db-0 ]
787+
Slaves: [ hn1-db-1 ]
788+
Resource Group: g_ip_HN1_03
789+
nc_HN1_03 (ocf::heartbeat:azure-lb): Started hn1-db-0
790+
vip_HN1_03 (ocf::heartbeat:IPaddr2): Started hn1-db-0
791+
</code></pre>
792+
793+
You can test a manual failover by stopping the cluster on the hn1-db-0 node:
794+
795+
<pre><code>[root@hn1-db-0 ~]# pcs cluster stop
796+
</code></pre>
797+
798+
782799
## Next steps
783800

784801
* [Azure Virtual Machines planning and implementation for SAP][planning-guide]
785802
* [Azure Virtual Machines deployment for SAP][deployment-guide]
786803
* [Azure Virtual Machines DBMS deployment for SAP][dbms-guide]
787-
* To learn how to establish high availability and plan for disaster recovery of SAP HANA on Azure (large instances), see [SAP HANA (large instances) high availability and disaster recovery on Azure](hana-overview-high-availability-disaster-recovery.md)
804+
* [SAP HANA VM storage configurations](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-vm-operations-storage)

0 commit comments

Comments
 (0)