Hi!
I’m coming to you with the following issue. Our customer saw a sudden increase in Disk Library usage. Turns out a bunch of jobs weren’t getting aged anymore because their respective subclients were re-associated to a different Storage Policy. This makes sense as the cycle criteria part of the retention wasn’t being hit. However, according to the documentation, Commvault should drop the cycle criteria and age solely on days:
“If a subclient is re-associated to a new storage policy, the job retention is dependent on the following factors”
“The cycle retention specified in the old storage policy is ignored. Only the retention days specified in the old storage policy are honored after a full backup job is performed using the new storage policy. “
KB article: https://documentation.commvault.com/11.25/expert/11977_data_aging_frequently_asked_questions.html
A full backup has been taken on the new Storage Policy, but the jobs on the old Storage Policy are being kept and aren’t being aged.
Are we missing something? Do we need to adjust anything?
Thanks.
Jeremy