Recently, I migrated our SAP HANA environment to use the Veeam backup plugin, replacing the old Commvault plugin. The process had a few challenges that I want to share for anyone doing something similar.
The Problem
After uninstalling the Commvault plugin, I noticed that some old configurations were still on the system. This was preventing the Veeam HANA Plugin from being applied correctly. The issues were mainly caused by old configuration files and symbolic links that needed to be adjusted manually.
!-->
!-->
How I Solved It
1. Removing other plugin completely
In SAP HANA, I used specific commands to unregister the old backint and make sure nothing was left behind.
2. Adjusting configuration files
Some Backint files needed to be renamed or edited to make room for Veeam.
Example
mv hdbbackint hdbbackint.old !-->
!-->
3. Setting Up Veeam
Once everything was ready, I ran the SapBackintConfigTool to register the databases in Veeam:
SapBackintConfigTool --wizard During the wizard, I provided:
-
Backup server name
-
Port
-
User
-
Repository
Note: Make sure the user has the necessary permissions on the repository to allow backups and restores. Additionally, confirm that the user has access to the relevant pool. Without proper pool access, the Veeam HANA Plugin cannot communicate with the pool, which will cause the configuration to fail. Ensuring these permissions helps prevent errors and guarantees a smooth setup of the Veeam backup plugin.
!-->
!-->
4. Validating Everything
After the wizard, all SIDs (HDQ, HDD, and H4C) were configured correctly. The Veeam plugin was fully operational.!-->!-->!-->
!-->
