SAP Landscape Management 3.0, Enterprise Edition

Performing a 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. SAP Landscape Management stops all instances of other systems that are non productive SAP HANA systems.

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.

  • SAP Host Agent 7.20 SP 191 or above

  • You have selected the Show Advanced Shutdown Options when Stopping Operations checkbox during engine configuration.

    For more information, see Configuring Engine Settings.

  • The secondary system is independently up and running.

  • You have assigned the client connect address for the automatic IP redirect during system replication takeover.

    For more information, see Instance Properties.

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

  1. Choose Operations.
  2. Choose Systems from the tabs.
  3. From the Operations dropdown of the secondary system, choose Start of the navigation pathSAP HANA Processes Next navigation step TakeoverEnd of the navigation path.
    All steps included in the process are displayed in a graphical form.
  4. Choose Takeover.

    The former primary is now in status Not Running, the former secondary is now in status Running.

    • On the Configuration screen, SAP Landscape Management displays two primary systems.

    • To avoid data inconsistencies, the system automatically stops a running primary database during the takeover process. Consequently, clients cannot access the database.

      • The system deactivates all active virtual cluster IP addresses on the primary system.

      • The system activates all inactive virtual cluster IP addresses on the secondary system.

Next Steps

  1. Register the former primary system as the secondary system when it becomes available again.

    For more information, see Registering a Secondary Tier for System Replication.

  2. Execute the Failback.

    For more information, see Performing a Failback.

Monitoring System Replication

Related Information