Skip to main content

I have a two node standard SQL Always On Group. The primary node is in the primary data center (dc1) and the secondary node is in our secondary data center (dc2). When the AG is failed over to the secondary in dc2, the backup is trying to use the storage policy configured on the AG client which is in dc1 That does not work. Is there a way to automatically force the failed over node to use the storage policy assigned to the secondary node in dc2, which has the correct storage policy?

I hope that makes sense. 😊

Hi @tgladson,

 

You should be able to accomplish what you want to do with the configuration below:

 

https://documentation.commvault.com/2022e/expert/129182_using_storage_policies_in_same_region_for_backups_of_sql_always_on_availability_groups.html

 

 

Good afternoon.  Please refer to this documentation.  It should resolve this issue.

https://documentation.commvault.com/2022e/expert/129182_using_storage_policies_in_same_region_for_backups_of_sql_always_on_availability_groups.html

@Mike H and @Orazan thanks for the link you both sent. I gave it a try and it did not work, so I’m not sure that’s what I need or I’m not doing it right. I only put in the client that is the secondary node in the AG and is in dc2 in my example.

Here’s what I have:

agclient with storage policy (sp1) which consists of:

client1 in dc1 (primary) with same storage policy as agclient (sp1)

client2 in dc2 (secondary) with storage policy (sp2)

Could you give me an example of what goes into the Client Computer Group based on that example?

 

Thanks!

Reply


Terms & ConditionsCookie settings