From d0d7655dc653f99dacca2d6c7c8c25c046311a92 Mon Sep 17 00:00:00 2001 From: Dmitri Popov Date: Fri, 8 Dec 2023 16:05:49 +0100 Subject: [PATCH] Fix master-slave --- xml/s4s_components.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xml/s4s_components.xml b/xml/s4s_components.xml index 8bb3bdaa..3e57baa6 100644 --- a/xml/s4s_components.xml +++ b/xml/s4s_components.xml @@ -128,11 +128,11 @@ with the pure &sap; solution, takeovers can be automated. - It is configured as a master/slave resource: The master assumes + It is configured as a parent/child resource: The parent assumes responsibility for the &hana; databases running in primary mode, whereas - the slave is responsible for instances that are operated in synchronous - (secondary) status. In case of a takeover, the secondary (slave resource - instance) can automatically be promoted to become the new primary (master + the child is responsible for instances that are operated in synchronous + (secondary) status. In case of a takeover, the secondary (child resource + instance) can automatically be promoted to become the new primary (parent resource instance).