Skip to main content

Validate backups regularly but not all at once?

Regular Poster
Posts: 23
Comments: 82

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).

Forum Hero
Posts: 29
Comments: 9631
mvp

Top

Coyote, this option is already available to you from the Advanced Options - Validation settings for your backup tasks.

See the ATIH 2017 User Guide: Backup validation option where it states:

You can specify the following settings:

  • Validate backup when it is created - Select to check the integrity of the backup version immediately after backup. We recommend that you enable this option when you back up your critical data or system disk.
  • Validate backup regularly - Select to schedule validation of your backups to ensure that they remain "healthy".

    The default settings are as follows:

    • Frequency: once a month.
    • Day: the date when the backup was started.
    • Time: the moment of backup start plus 15 minutes.
    • Advanced settings: the Run the validation only when the computer is idle check box is selected.

    Example: You start a backup operation on July 15, at 12.00. The backup version is created at 12.05. Its validation will run at 12.15 if your computer is in the "screen saver" state at the moment. If not, then the validation will not run. In a month, August 15, at 12.15, the validation will start again. As before, your computer must be in the "screen saver" state. The same will occur on September 15, and so on.

    You can change the default settings and specify your own schedule. For more information see Scheduling.

Regular Poster
Posts: 23
Comments: 82

Top

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).

ATI-ReValidationOptions.jpg

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".

Forum Hero
Posts: 29
Comments: 9631
mvp

Top

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 by Steve Smith

Regular Poster
Posts: 23
Comments: 82

Top

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?

Forum Hero
Posts: 29
Comments: 9631
mvp

Top

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.