SAP Landscape Management 3.0, Enterprise Edition

Near Zero Downtime Takeover Workflow

This section shows the workflow for performing a near zero downtime 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.
You enable log retention propagation to retain the log based on the smallest savepoint log position in the whole system replication landscape. Ignores open database connections and stops an instance immediately. Enables system replication on the primary system or tier 2 secondary system (source system) and provides a logical name for the system. Ignores open database connections and stops an instance immediately. Registers the tier to the preferred sibling. Performs a start operation without considering external dependencies. Reregisters the secondary to the previous primary. Performs a start operation without considering external dependencies. Enables the table preload. Enables the table preload for a tenant database on the secondary tier. Table preload reduces takeover times. Waits until system replication is active. Ignores open database connections and stops an instance immediately. Enables the table preload. Enables the table preload. Waits for preloading of tables. Uses the configured database administrator user password in SAP Landscape Management configuration to set the SRTAKEOVER key Enables a quiesce check. Enables a quiesce check. Enables a system status in which further data changes are not allowed. RFC calls are no longer possible until disable quiesce is called. Enables a system status in which further data changes are not allowed. RFC calls are no longer possible until disable quiesce is called. Waits until all schema user connections to SAP HANA are closed. Deactivates the tenant IP address. Deactivates the virtual cluster host names. Ignores open database connections and stops an instance immediately. Checks the replication status from the replication status repository central host before a takeover is triggered. Performs a takeover operation. This step does not automatically stop the primary system. Deletes a previously created SRTAKEOVER key. Activates the virtual cluster host names. Activates the tenant IP address according to the configured sequence of the SAP HANA node in the potential nameserver candidates. Disables quiesce. Disables a quiesce check. Disables quiesce. Disables a quiesce check. Disables a quiesce check. Disables a quiesce check. Waits until all schema user connections to SAP HANA are closed. You enable log retention propagation to retain the log based on the smallest savepoint log position in the whole system replication landscape. You enable log retention propagation to retain the log based on the smallest savepoint log position in the whole system replication landscape. You enable log retention propagation to retain the log based on the smallest savepoint log position in the whole system replication landscape. You change the log retention mode. You enable system replication on the primary system or tier 2 secondary system (source system) and provide a logical name for the system. Disables log retention. You disable log retention propagation. You disable log retention propagation. You disable log retention propagation. Sets the log retention mode of the secondary to force_on_takeover. This allows an optimized resync of the primary in multitarget replication ennvironments.