Veeam Plug-In for SAP HANA — Support for SAP HANA System Replication

KB ID: 4391
Product: Veeam Backup & Replication | 11
Published: 2023-01-24
Last Modified: 2023-01-24
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article provides information about using Veeam Plug-in for SAP HANA to protect SAP HANA System Replication.

Solution

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.

Independent

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.

Federated

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.

  Independent Federated
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  

Experimental
Support Only

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.

Federated Configuration

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.

Implementation

After configuring the Veeam Plug-In for SAP HANA
 

  1. Edit the veeam_config.xml file located in:
/opt/veeam/VeeamPluginforSAPHANA
vi /opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml
veeam_config location
  1. Within the “PluginParameters” node, append a unique name for the “customServerName” value.

    In this example, “DRPREPO” was used.
  1. Update the veeam_config.xml on each of the related nodes in the system replication setup so that each group of replication nodes has its own shared but unique customServerName value.
If a new node is added, the veeam_config.xml on that node must be modified to match.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.