For more information about the replication features that SAP supports, go to the SAP website, HANA System Replication.
Important
-
The Commvault SAP HANA agent automatically detects and manages SAP HANA takeovers for IntelliSnap backups. Therefore, you no longer need to make manual changes.
-
After you perform the restore operation for HANA snap replication, you must manually re-enable the replication.
-
After the SAP HANA takeover process, you need to re-create the HDBUSERSTORE key on all the nodes with the primary site nodes in the beginning, followed by secondary site nodes. This is applicable only if the custom HDBUSERSTORE key is used for SAP HANA instance configuration in Commvault interface.
-
If the
Restore will be retried on next node in client listevent message appears for a snap restore job after failover, the Commvault software automatically resumes the restore job using the next node available in the client list.
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).
When you fail over the HANA service from node1 to node2, run a full backup of the database.
Procedure
-
Install the SAP HANA agent on all the primary and secondary nodes or VMs that are part of the same SID.
-
Create a pseudo client and add all the nodes to that pseudo client.
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.
For backups to work after a SAP HANA takeover, create a the SAP HANA HDBUSERSTORE key to connect to the SAP HANA database. For more information, see Creating the SAP HANA HDBUSERSTORE KEY.