SAP Landscape Management 3.0, Enterprise Edition

Assigning Replication Status Repository

Before performing a takeover process using SAP Landscape Management, you can ensure that SAP HANA system replication is in sync.

Prerequisites

  • A replication status repository has been configured.

    For more information, see SAP HANA Replication Status Repositories.

  • You have permission Service,Resource(CriticalCustomOperation).

    For more information, see Standard Permissions.

  • SAP Adaptive Extensions have been installed with the minimum patch level 41.

    For more information, see SAP Adaptive Extensions.

  • The primary master node status is Not running Not Running or Running Running.

Context

The replication sync status will be retrieved by the repository host.

The validation HDBRepStatusPrim retrieves the replication status from the primary site. The validation ReplicationStatus validates the replication status of a database.

Validations for Instances

Procedure

  1. Choose Operations.
  2. Choose Systems from the tabs.
  3. From the Operations dropdown for the primary master node, choose Start of the navigation pathSAP HANA Processes Next navigation step Assign Replication Status RepositoryEnd of the navigation path.
  4. Choose the SAP HANA replication status repository.
  5. Choose Next.

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

  6. Choose Refine Execution.
  7. Specify the maximum accepted age of the replication status on the NFS share in seconds.

    If the age of the replication status on the NFS share is older, the status is considered as "out of sync”.

  8. Choose the replication status repository.
  9. Optional: Change default installation directory of the HA/DR provider scripts.

    The default directory should be available on all nodes of a scale-out cluster. Ensure that the scripts are installed and available on all nodes in this directory.

  10. Optional: To stop processing on the primary instance in case the replication status share is not available and replication is out of sync, set Strict Handling to True. With that you can avoid data loss.

    You can then no longer write on the primary instance.

  11. Optional: Enter the timeout while writing to the replication status share.

    This is the maximum amount of time the primary instance will wait for the hook in case of a stale NFS share.

  12. Optional: Enter the interval for the file system check in seconds.

    Ensure that the interval for the file system check is smaller than the accepted age of the replication status.

  13. Choose Execute.

Next Steps

Start the primary system.

For more information, see Starting Systems and Instances.

SAP Landscape Management will retrieve the replication sync status of secondaries from the repository host.