As you have many storage policies, please run the report for each storage policy copy you are interested to know what jobs are there and the reason for their retention.
Regards.
This report was from the Forecast and Compliance Report but I need to know which jobs are not expiring.
Could you help me? @Ledoesp
The Storage Polices of the Forecast and Compliance Report:
CommServe Timezone Calendar Name: Standard Retain for 15 days 2 cycles, Archiver data retain for 15 days For Weekly Full Rule the week starts on Friday; Retain One Full Every Week for 60 days; 1 Grace Days For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days; 1 Grace Days For all rules keep the last full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 15 days 2 cycles, Archiver data retain for 15 days For Weekly Full Rule the week starts on Saturday; Retain One Full Every Week for 60 days; 1 Grace Days For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days; 1 Grace Days For all rules keep the last full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 15 days 2 cycles, Archiver data retain for 15 days For Weekly Full Rule the week starts on Saturday; Retain One Full Every Week for 60 days; 1 Grace Days For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days; 1 Grace Days For all rules keep the last full backup of time period
Storage Policy Copy Properties: (SP_Faro/Primary)
CommServe Timezone Calendar Name: Standard Retain for 15 days 2 cycles, Archiver data retain for 15 days For Weekly Full Rule the week starts on Saturday; Retain One Full Every Week for 60 days; 1 Grace Days For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days; 1 Grace Days For all rules keep the last full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 90 days 1 cycles, Archiver data retain for infinite For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 730 days 1 cycles, Archiver data retain for infinite Retain One Full Every Year for 1095 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 60 days 1 cycles, Archiver data retain for infinite For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days Retain One Full Every Year for 730 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 60 days 1 cycles, Archiver data retain for infinite For Monthly Full Rule the month starts on 1; Retain One Full Every Month for 180 days Retain One Full Every Year for 365 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 90 days 1 cycles, Archiver data retain for infinite Retain One Full Every Year for 180 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 30 days 1 cycles, Archiver data retain for infinite For Weekly Full Rule the week starts on Friday; Retain One Full Every Week for 90 days For all rules keep the first full backup of time period
CommServe Timezone Calendar Name: Standard Retain for 60 days 1 cycles, Archiver data retain for infinite
Basically, jobs that do not expire are the ones not meeting the retention defined at the storage policy copy level. As you provide some details, each storage policy copy has defined a basic retention in days and cycles, in some cases some extended retention rules are in place.
@Fernando Souza , the above answers are solid. What you want to do overall is look at what jobs you should EXPECT to be there and look for anything outside that expectation. A given full will normally prune X days after its last Incremental (where X equals days of retention).
At a VERY high level, you generally should not have any jobs unaged that are older than:
Days of Retention + Days between Fulls
Now, extended Retention and Cycles will change that, but assume the following:
8 days of retention + Weekly fulls (so 7 days between Fulls) = 15 days of data at most in that copy.
With that in mind, you want to look at any jobs that are OLDER than that time period and see what the reason for not pruning states in the report and go from there.
If you can share some examples, I’ll be happy to advise!
Hello @Mike Struening Thanks for your help, i need know about the jobs didn´t have pruning and jobs have a dependency to other jobs.
I send the Data Retention Forecast in attach.
@Mike Struening
in another example(My laboratory) i have disk media to free, how can i free this space?
Thanks, @Fernando Souza !
I had a review and most of the report looks fine.
However, you have a decent number of old backups hanging around like these showing SP_Change_Keep_Last_Full.
What happened here is that you moved a subclient from one Storage Policy to another, and we are holding the last Full that ran on the OLD Policy until one runs on the NEW policy.
Without knowing, my assumption is that no new backup ran for whatever reason. Take a look at the report and search for the jobs held for “SP_Change_Keep_Last_Full”. You may want to manually remove them from any disk based copies.
You can also click the reason for more information.
Also, small note, you can see in my screenshot that I was doing a ‘Find’ on “retain for”. That’s my little shortcut to go through these reports quickly since it jumps to the next copy and shows me the oldest jobs first
Let me know if that helps!
@Mike Struening
in another example(My laboratory) i have disk media to free, how can i free this space?
All Storage Polices that begin with “OLD_” are associated with Media Agent “pt-acv”, since Commvault does not re-associate existing Storage Polices with a new deduplication engine.
In the old scenario they copied data to tape and in the new scenario all data goes to disk;
in the new scenario: if the primary copy is equal to or less than 365 days, if is is an auxiliary copy it will use the server “pt-acv2”.
To ensure that the data was correctly removed from tape to disk, the following SP´s were created (SP\Migration_From_Tape_to_Disk): OLD_SP_Lisboa_BD_PROD OLD_SP_Lisboa_Infinito OLD_SP_Lisboa_BD_FS_3Y OLD_SP_Lisboa_BDarch_PROD OLD_SP_Lisboa_Extendida OLD_SP_Lisboa_Normal
Purchased of a new Media Agent to distribute to this load with the new MA, help me how should i distribute this data with the new MA.
and in attach, ik organize the Storage Pools(without SP starting with “OLD_”
Hello @Mike Struening
I was checking and for example, when I search for "SP_CHANGE_KEEP_LAST_FULL" I verified that all of these search jobs are already expired, can I remove them, correct?
And i saw this search and found to be related to SP: “OLD_”
And another question, for remove, just disable and enable backup, then start aging and release space, is it correct?
@Fernando Souza , if you are 100% sure you no longer need those jobs, view the jobs on that Copy, right-click and hit Delete, then run Data Aging.