We have an incremental backup that ran on 29 August and completed at 19:11. The storage policy has retention set to 7 day and 2 cycles. On 10 September we unable to restore that data because it has aged. Based on our understanding that backup should only have aged on 12 September before the 2 cycles completed.
What could be the reason for this “early aging” of that job?
Storage policy retention
Hi
Run the “Audit Trail”, update the job ID in the “Search string” and try to get any info regarding that job.
If you have any old DB from September 1st Week, raise a case with the support so we can try to get the reason for that aging.
Regards,
Wasim
You did not show the complete job history. How often are Full jobs running?
If you run a Full every day, for instance, “2 Cycles” would be met in only “2 Days”.
If you want to guarantee 14 days of job history, you need retention to be “14 Days”.
Thanks,
Scott
Your job history has 10 days and 2 cycles. Technically this exceeds your configured retention settings for 7 days and 2 cycles.
As I mentioned, if you want to guarantee at least 14 days of data, I recommend changing your retention settings to 14 days.
Thanks,
Scott
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.