Hi @YYZ,

Currently there are only 2 ways in which new subclient associations to a Storage Policy are prevented:

1. If the Query and Insert time on the associated DDB is under-performing, new subclient associations are automatically disabled.
   1. In this scenario, existing subclients will still continue to run as expected, but nothing new can be associated.
2. The option to ‘Hide and Disable Storage Policy for Backups’ is selected in Storage Policy properties.
   1. While this will prevent new subclients from being associated, this would also prevent existing subclients from being able to back up, making this not ideal for you.

Currently, there is no way to achieve your end goal while the associated DDB is performing well.  If there is a valid use-case for this, we can ask engineering to add an enhancement for this in the future.

-Brian Bruno

Thanks Bruno

(2) - as you said, you need to vacate the subclients

(1) - I’ve experienced that in the past -

      I had thought of a possible ‘hack’ to ‘inject’ a fake (very high)  QI time into the commserve SQL

      (Just joking )

@YYZ : Do you mean associating new subclients to DDB or to storage policy?