Data Aging after changing the client name and moving to another client group

Hi @gary mcneely 

Thanks for making this post, data aging is something that tends to be a somewhat common concern and while there can be many reasons there is a few common culprits.

Your name change and client group modifications won’t alter the retention, and that’s a good thing! we wouldn’t want to accidentally prune data just because the name changed if you didn’t expect it to!

• The best way to determine why any job is not meeting retention is to navigate to reports > forecast report (also referred to as Data Retention Forecast and Compliance Report) 
• Within this report leave the settings default on the first tab and second tab
• On “Library/storage policy” set this to either the storage policy copies in question or the library in question then hit ok
• This report will list all jobs within the selected storage policy copies or libraries starting from the oldest at the top for each one
• You can search for your job id in here and it will detail why this has not yet met retention
• You mentioned that you disabled backup activity thus you will likely see the report state basic_cycles as your reason for not meeting retention

As you have advised you disabled the schedule, my gut feel on the information provided is that cycles are not being met. 

For data to age it must meet the storage policy rules for days and for cycles. If you have stopped the client from backing up anymore no more cycles will be created and thus will not be met and the jobs will be retained.