Skip to main content
Answer

Automatic association and deassociation of client/subclient in storage policy in all secondary/Aux copies: Does it always occur automatically?

  • August 1, 2025
  • 1 reply
  • 19 views

Forum|alt.badge.img+11

I ran the “Subclients without Secondary Copies” report and there are several records that are there.  It appears in only 2 cases that a subclient was not associated with any aux/secondary copies, and in several more cases there are associations in secondary copies that are still “there” but for delicensed clients.

Also: It appears it is occurring with clients/subclients tied to just *one* of my storage policies. All other clients/subclients associated with all my other storage policies look “ok” (and are not showing up on this report).

I was under the impression that once you associated a client to a storage policy, the “association” of the client to the secondary copies happened automatically. And when you delicensed a client, the associations were automatically removed. Is this true/supposed to happen always or are there caveats to these assumptions?

I’m feeling there is a config or something ‘special” about this single storage policy (it is very old) but I don’t know what it would be that would cause storage policy secondary copy “associations” to not be auto added or removed whenever new clients are added or licenses released. 

Best answer by Pradeep

Hi ​@tigger2 ,

 

Sub client associations are defined at the storage policy level. By default, any new copy created under the storage policy other than the primary copy The succulents are automatically added to the secondary (auxiliary) copy. This association remains until it is manually de-associated from the secondary copy system created schedule.

1 reply

Forum|alt.badge.img+12
  • Vaulter
  • Answer
  • August 2, 2025

Hi ​@tigger2 ,

 

Sub client associations are defined at the storage policy level. By default, any new copy created under the storage policy other than the primary copy The succulents are automatically added to the secondary (auxiliary) copy. This association remains until it is manually de-associated from the secondary copy system created schedule.