SAP Landscape Management 3.0, Enterprise Edition

Takeover Workflow

This section shows the workflow for performing a takeover in a graphical form.

Process Step Legend

Step is mandatory.

Step is optional and will be skipped when executing the custom process on an entity that does not fulfill the constraints defined for this custom process.

Step must be executable on all resolved entities in order to execute the custom process.

Step is optional and must be executable on all resolved entities. This step will be skipped if there are no resolved entities. If there is at least one resolved entity, the step cannot be skipped.

NoteThe following image contains links to more information.
Deactivates the tenant IP address on the primary system. Activates the tenant IP address according to the configured sequence of the node in the potential nameserver candidates. Deactivates the virtual cluster host names. Ignores open database connections and stops an instance immediately. Performs a takeover operation. This step does not automatically stop the primary system. Activates all inactive virtual cluster host names on the secondary system. Avoids split brain situations by checking the clients such as SAP NetWeaver ABAP or Java to ensure that they cannot connect to SAP HANA. Avoids split brain situations by checking the clients such as SAP NetWeaver ABAP or Java to ensure that they cannot connect to SAP HANA. Checks the replication status from the replication status repository central host before a takeover is triggered. Sets the log retention mode of the secondary to force_on_takeover. This allows an optimized resync of the primary in multitarget replication ennvironments. Ignores open database connections and stops an instance immediately. You enable log retention propagation to retain the log based on the smallest savepoint log position in the whole system replication landscape. You enable system replication on the primary system or tier 2 secondary system (source system) and provide a logical name for the system. Registers automatically to the last tier in the replication chain. Only possible if the instance was already in this replication chain. Performs a start operation without considering external dependencies. You enable system replication on the primary system or tier 2 secondary system (source system) and provide a logical name for the system. Reregisters the secondary to the previous primary. Performs a start operation without considering external dependencies. You disable log retention propagation. Ignores open database connections and stops an instance immediately. Retains the log based on the smallest savepoint log position in the whole system replication landscape. This SAP process step is relevant for multitarget system replication scenarios. Disables log retention. Enables client access to new primary. Reregisters secondaries of replication siblings. Registers replication siblings to new primary. Shutdown primary to avoid split brain situations.