Configuring SAP HANA Replication

For more information about the replication features that SAP supports, Go to the SAP website, HANA System Replication.

Important: If you have Commvault Service Pack 10 or earlier and you have a multinode SAP HANA database, then you must set the first node to a node that can successfully run hdbsql commands. After a "takeover" event, you must update the order of the nodes to ensure that you can run backups from the CommCell Console or from the Commvault scheduler. You can perform this operation by using the Commvault command line interface. For more information, see Modifying SAP HANA Instances Using the Commvault Command Line Interface.

For Commvault Service Pack 11 or higher, the Commvault SAP HANA agent automatically detects and manages SAP HANA takeovers for streaming backups, so you no longer need to make manual changes. In the case of IntelliSnap backups, you must change the order of the physical nodes to keep the current primary node as the first node for the SAP HANA instance.

Backups that you perform from SAP HANA Studio are not affected by the node order as long as the node appears on the instance details (Instance Properties dialog box, Details tab, Hana Database Instances box).


  1. Install the SAP HANA agent on all the primary and secondary nodes or VMs that are part of the same SID.
  2. Create a pseudo client and add all the nodes to that pseudo client. The order must be the primary node and the secondary nodes.

    For information on creating the client on a clustered and non-clustered setup, see Configuring SAP HANA for a Multi-Node or Clustered Environment.

What to Do Next

In SAP HANA Studio, configure backint for the database.

Last modified: 4/8/2020 10:56:06 PM