Performing a Near Zero Downtime Takeover

If your primary system is not available, due to a disaster or planned downtime for example, and you have decided to fail over to the secondary system, you can perform a takeover on your secondary node with near Zero Downtime.

Prerequisites

You have the authorization to perform the operation.

For more information, see Standard Permissions.
You have assigned the roles and groups required to perform the operation.

For more information, see Standard Roles and Groups.
You have set up and configured system replication.

For more information, see Setting Up System Replication.
The secondary system is independently up and running.
You know the operation modes that you can use.

Note If you want to use operation mode logreplay or logreplay_read access, ensure that your log retention settings allow an optimized data transport.

For more information, see System Replication Operation Modes.
Recommendation
Assigning Replication Status Repository

Context

When the primary system replicates data changes to more than one secondary system, SAP Landscape Management uses forced log retention and log retention propagation. The log will be retained during replication for all direct secondaries until a takeover is executed. During takeover, the parameter is set to force. This means the log will be retained independently of any secondary system. Log retention propagation is used to retain log based on the smallest savepoint log position in the whole system replication landscape.

Procedure

Choose Operations.
Choose Systems from the tabs.
From the Operations dropdown of the secondary, choose SAP HANA Processes Near Zero Downtime Takeover.

All steps included in the process are displayed in a graphical form.

Note To view more details or to change paramters and settings such as the log and operation mode for an individual step, select a process step.
Choose Execute.