Skip to main content
commvault.com commvault.com

Hello all,

maybe you can help me!?

The following situation at the customer:

Linux system with HANA DB (all HANA specific filesystems connected via NFS)
the customer has one IP for the host and one VIP (+DNS) for HANA (same subnet). The idea is that he can move the HANA system to a stronger host at any time without having to change anything in the HANA configuration (hence NFS).

How do I manage to add the system 2 times in Commvault (1 x under its real host name for OS backups and 1 x as virtual system with the VIP and the HANA DB name (DNS entry for the VIP) for all HANA specific connections? So far Commvault takes sometimes one and sometimes the other IP as primary IP when I create the client and when I want to include the other one I fail. Under Dataprotector this was easy, because there was the possibility to enter a virtual host. So the DB integrations could run over the VIP (and it didn't matter where the DB was running) and the host backup over the host entry

Best regards

 

Frank

Hi Frank,

If I understood it right, 

  • You have a OS level cluster which has a VIP for the cluster
  • which host the hana DB that uses teh VIP for the DB
  • the hdbuserstorekey for the HANA DB is configured using the VIP

If the above understanding is correct, you can create a cluster pseudo client in commcell for the Physical nodes https://documentation.commvault.com/commvault/v11_sp20/article?p=4990.htm

Use the VIP for the cluster client hostname.

And then in the HANA psudoclient, you can define the Cluster client as the node for the HANA database, provieded the hdbuserstorekey is configured using VIP.

https://documentation.commvault.com/11.24/expert/22343_creating_sap_hana_pseudo_client.html

 

If you face issues configuring or backinup with this config, I’d suggest to raise a trouble ticket for it.

As per books online it shows it’s supported for unix cluster :

https://documentation.commvault.com/commvault/v11_sp20/article?p=5041.htm

 

Thanks and regards

Abdullah

 

You can multi instance to create 2 clients and set the hostname of each client to IP address instead of DNS. Not sure how that would help for the HANA with the vIP if it moves to another host, there wouldn’t be any CV software there to do backups? Or did you just mean storage backend may change without the vIP and current host changing?

 

https://documentation.commvault.com/11.24/expert/1841_multi_instance_installations_01.html

 

thanks for your answers!

 

sorry for the late reply, but i am currently still struggling with other CV issues as well. I will try to use the pseudo cluster client even if it’s not a "real" cluster 

Reply


Terms & ConditionsCookie settings