Skip to main content
Question

Re-Associate clients to different storage policy


Forum|alt.badge.img+1

Looking for a automated way to re-associate client in a storage policy to a different storage policy.

Our DR/Failover plan requires us to different libraries, Data paths When we failover our Comserve to our Secondary site. Once our Primary site has failed over to secondary site we will bring up the Commserve and re-associate the client in “primary Site/s Storage Policies” to “Secondary Site’s Storage Policies” so backups will then start backing up to Storage located at Secondary Site. Thus for the reasom that I’m looking for a script/ Automated way to re-associate several Primary Site SP’s to their counterpart Secondary Site SP’s

3 replies

Forum|alt.badge.img+3

Hi ​@Rixon01,

I understand that you want to re-associate clients or subclients with a different storage location after a failover, so that they point to the Storage Associate at the Secondary Site.

You can configure the data path for secondary storage at the copy level. This way, during a failover, the secondary storage will have a preferred data path set at the storage policy copy level, as detailed here ->
Copy Properties - Data Path Configuration

If you prefer to modify the subclient association using a script, you can update the subclient properties with the following Update_CopyAssociations.xml file as outlined in the documentations on Updating Subclient Associations of a Storage Policy Copy.

Regards,

Dheeraj Shetty


Forum|alt.badge.img+1
  • Author
  • Byte
  • 2 replies
  • April 2, 2025

In my Storage Policies I have the Primary copy configured with data paths that backup to primary location. Then a second copy that copies the same data to secondary location. When failover/DR occurs, couldn’t I “Reverse the Streams” by promoting the secondary copy to be the primary copy, then the Primary copy would become the secondary copy?

 


Forum|alt.badge.img+3

Hi ​@Rixon01 ,

If your primary copy is stored at the Primary Site and the secondary copy is stored at the Secondary Site, you can promote the secondary copy to primary once you failover to the DR Site. However, the secondary copy must be synchronous. Additionally, please confirm whether the retention settings for both the primary and secondary copies are the same or different. Thank You!

 

Regards,

Dheeraj Shetty

 


Reply


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