Skip to main content
commvault.com commvault.com
Question

Oracle Data Guard failover

D
Bit
Forum|alt.badge.img+1

Hi,

 

I’m having problems with a Commvault Oracle Data Guard configuration. I have a Data Guard pseudo-client which handles the backups for the environment which has 2 databases on 2 different hosts: dbhost01 and dbhost02. It is configured to run backups on the primary node. A few days ago a database failover happened (from dbhost01 to dbhost02), it was successful, so no issues with that, currently the primary database is on dbhost02.

My problem is that since the failover the commvault backups cannot run, because it is still trying to reach the database on dbhost01 (which is shutdown). It sees that the database on dbhost02 is open, but does not even try to start the backup there.

What is the correct way to configure this? The whole point of having this Data Guard configuration in Commvault is that we don’t have to modify anything in commvault when a failover/switchover happen, so I’m looking for a solution that provides this.

 

Thank you for any tips, solutions, etc.

 

Daniel

2 replies

CV_GK
Vaulter
Forum|alt.badge.img+5
  • CV_GKVaulter
  • Vaulter
  • 71 replies
  • April 22, 2025

Hi ​@DanielSz 

Does check readiness of pseudo client work?

D
1 person likes this
  • D
    DanielSz
D
Bit
Forum|alt.badge.img+1
  • DanielSz
  • Author
  • Bit
  • 1 reply
  • April 23, 2025
CV_GK wrote:

Hi ​@DanielSz 

Does check readiness of pseudo client work?

Hi,

Thank you, your comment gave me an idea and it lead to success in the end :)
The client readiness check was fine before, except for the shutdown database. For some reason now it gave Not ready for the client, stating that there is communication failure between dbhost01 and dbhost02. I tried cvping from those hosts and it worked without issues. After a lot of checking and comparison to other configurations I noticed that the 2 clients (dbhost01 and dbhost02) has the hostname in their configuration while other systems have the IP address. Both should work (and used to work), but after changing the hostnames to IP addresses everything works fine, client readiness shows ready and the backups work on dbhost02.

dude
1 person likes this
  • dude
    dude

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings