Extra backup time required on full backups?
Greetings..
As I read about the lengthy backup times with ATI2020, the discussions all seem to imply that the long times relate to 2020 re-verifying all members of a string in incremental and differential versions. I only do FULL backups, setup to retain only 3 backups. They are not scheduled, but started manually after changes, installs, updates, etc, and includes the C drive (system) and D drive (data).
Prior to 2020 the backup time and verify time was very close to same. With 2020, the backup time is around 2 hours and verify time is 9 or 10 hours!! Is this normal for full backups as well as well as other methods??
I may have miss-read, or miss-understood what I read, about when the extra verify time comes into play! Or, is that just a function of 2020 that has to be planed for? What is 2020 doing that requires the additional verify time on FULL backup?
Thanks,
Robert


- Log in to post comments

Thanks, Steve,
You probably just hit the correct explanation! If I specify in my task to do a full backup, and also specify to save the last 3 backups, it will validate those three as well as the current one, even though those were already validated when they were created!!!
I sure didn't understand it that way. Thanks for clarifying it! I guess the best aproach is your method of back up without "validate when created" then manually start a validation.
Any chance that option may be altered in a future update to allow validation of only the current backup when created, as it was the many years I have used Acronis?
Thanks again, Steve
Robert
- Log in to post comments

Robert, this validation behaviour is new with the .tibx files in ATI 2020. There has been a lot of discussion about it since the early beta so we are hoping that it will be a temporary issue. We'll check again on the next release.
- Log in to post comments