Validate backups regularly but not all at once?
I see that I can re-Validate backups on some schedule. Assuming this is worthwhile...
Is there some way to spread out these re-Validations...such as to re-validate each every 30 days after creation?
I'm seeking to avoid re-validating ALL of them the same day.
p.s. I see that ATI will email me when disk space drops below my chosen threshold; I wish I could incorporate that threshold into Automatic Cleanup (which has parameters far less appealing to me).
Thank you very much for your very helpful reply, Steve!
I'm afraid that while I just read the manual, I missed that "Example" text. However, even now that I've read it, I cannot match the functionality it described to the Settings (which I had already examined before posting).
Specifically, I see options pick specific dates every month (to revalidate ALL my backups). Upon Event doesn't appear to have the "Month after image creation" functionality described in the "Example" text either.
The "Example" text is very exciting, but I don't see where to set Re-validations for a "Month after image creation".
When you select the option to 'Validate backup regularly' this should only apply to that one backup task that you set these options for, not for all your backups.
Acronis will create a scheduled validation task to perform this action at the interval that you select, i.e. this can be as shown in your screen image, Daily, Weekly, Monthly etc.
In reply to When you select the option… by truwrikodrorow…
I did understand that it applied to the one backup task, but since each task will have many chains/versions, I wanted each version re-verified monthly based upon it's creation date.
In other words, I'll run incrementals daily. And I don't see how to get daily re-validations of only those backups created the same date (say, the 24th).
Do all the versions of a backup task need to be re-verified all at once?
OK, I understand the confusion here... when Acronis does a validation, it validates the whole backup version chain(s) for the task where validation is set to run.
There is no need to try to validate individual files, but obviously, the larger the number of files in any chain, and the number of chains for the task, will cause validation to run longer.
The good point about incrementals is that these will normally be smaller because they only include the changes captured since the previous backup was created.
The downside for incrementals is that if you start creating very long chains of these, every one of the files is critical if you want to be able to recover using the version chain.