There are two methods to utilize Veeam Plug-In for SAP HANA when protecting nodes involved in SAP HANA System Replication.
Both methods use the same core Veeam Plug-In for SAP HANA installation and configuration steps for the source and target(s) of replication.
The Veeam Plug-In for SAP HANA treats each node as an independent machine. After takeover, changes must be done to realign existing backup data to cause the Plug-In to recognize the failover node as if it is the original node.
The Veeam Plug-In for SAP HANA deployed on each node is configured with a shared customServerName parameter so that the related nodes are seen as the same machine, allowing for a seamless transition after takeover.
|Compatible with Veeam Backup & Replication v11 and newer|
|Additional configuration must be done during the deployment|
|All nodes of the SAP HANA System Replication setup must authenticate to Veeam Backup & Replication using the same account|
|All nodes of the SAP HANA System Replication setup must use the same Backup Repository|
|After takeover, to access old backups, additional administration must be done||1|
|After takeover, backups will continue using existing backups seamlessly||2|
|After takeover, a new full backup must be created||2||Recommended 3|
|Configuration is Supported|
1 Federated configuration causes all nodes of the replication setup to be treated as the same machine. This means that after takeover occurs, restore operations function seamlessly.
2 With Independent configuration, each node of the replication setup is treated as a separate machine. After takeover occurs, backups from the new active node must start a new backup set.
3 When using Federated configuration, after takeover, the newly active node will continue using the same backup set as the previous node. It is recommended to create a new full backup but it is technically optional.
After Veeam Plug-in for SAP HANA has been installed and configured on each node, the Veeam Plug-In for SAP HANA configuration file on each related node needs to be modified to create a shared “customServerName” value. This customServerName value should be unique to the set of related nodes. With this value set in the event of failure or takeover, the new backups will still point to the same repository and will have access to older backups.
After configuring the Veeam Plug-In for SAP HANA
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case