Option "Retain Until" can delete job

Hey @Fernando Souza !  hope all is well!!

It looks like the job is on 3 copies.  The question here is “which copy is the first screenshot referring to?”

Can you run a Data Retention Forecast and Compliance report against the copy/library in question and see what it shows for that specific job?

Thanks!

@Fernando Souza,

First thing you want to look into is the reason why these jobs have not aged. You can run the Data Retention Forecast and Compliance” report against the storage policy copy in question. For example. in this case you would run it against the Primary copy under SP_FILESERVER_EXCHANGE”. 

This report will tell you a reason why this job has not aged. You can look at the reason for the job not aging and then understand the reason behind it in the following doc:

https://documentation.commvault.com/11.24/expert/11966_data_aging_troubleshooting.html#data-retention-forecast-and-compliance-report-error-codes

The reason why this is important is because if its a systemic problem you may want to fix it so you dont have to manually delete jobs every time. 

For the time being, to answer your question, you can certainly delete the job from the primary copy while still keeping it in tact on the tape copies. You can do so by viewing the jobs at the copy level:

1. Under policies > Storage policies > SP_FILESERVER_EXCHANGE > Primary.
2. Right click primary > view > jobs > uncheck the time range box to see all the jobs.
3. Select the job you want to delete > right click > delete job.
4. Right click the commserve > all tasks > data aging.

Hope this helps.
Regards

Hello @Mike Struening ,

The first screen is the backup expired, is it correct? and can i removed?
I will run the Data Retention Forecast and Compliance report, to view

Fernando,

The first screenshot is saying he backup should have aged out on 2nd Jan or Feb 1st depending on the format of the dates you use however it did not and the reason it did not, you will find in the forecast report. You should not need to manually delete jobs once they meet their retention so I would recommend checking out the forecast report to understand why the job didn’t age when it should have. ​​

Hello @Harsh Desai 

I understand that it had to expired and not expired, but why it didn´t expire?

One example:
JOB ID 115206 Retention is one year:

This job will expire on 25/05/2022(1 year after), but the status in the Forecast Report is as “green” and PRUNABLE, can i explain to me, please?

Thanks

I deleted some stale jobs manually, will this be deleted automatically from the library or I have to afterwards prune the data from the storage policy?