validating versions of backup
I created a full image b/up in january with a validation which was successful. I now find myself creating an incremental b/up which I combined with a request for a validation. As I look at the window while this is getting done, I see it tells me that it is 'validating all versions of the backup'. To me this seems to mean that it is not only validating the incremental version but the previous(ly validated) full image b/up as well. Is that absolutely necessary. I would not think it would be if the full image backup is already validated. I would also think that just validating the incremental one under these historical set of parameters I am describing would shorten the amount of time required to complete the incremental.
Has anyone thought this through?
The inc has no value without the full. If full is not good, the inc is useless.
There is really few options. The complete backup must be validated if the full chain is to have any value.
Some user get comfortable that the validation works and then stops validation does only occasional validation as a separate task.
My practice is validation with each backup.
Hi,
I seem to think that while this (and first) incremental b/up took only around 12Gb vs. the 45GB or so for the full image b/u I did (w/validation) around a month ago, that this incremental b/up+ validation process required far more time than the full image+validation did. Is that possible.
Suppose I had created this incremental b/up w/o validation and performed a manual validation later on, would this manual validation also proceed to (re-)validate the full image b/u.
In other words is there no way to bypass having to have each prior b/up validated when one creates an incremental b/up which gets validated?
No, this is not an option. This protects your data, but is inconvenient for most users that have a limited time window in which to perform a backup with validation. Many users turn off validation for this reason. A great option would be to ASK whether to validate the whole version chain or just recently created .tib file.
Regarding what you wrote re: "A great option would be to ASK whether to validate the whole version chain or just recently created .tib file.", does this firm have a suggestion box or the e-quivalent? As this MVP, perhaps you have an inside line to their tech personnel that handle upgrades and enhancements; enforcing the requirement the entire version chain is always validated is a less than good strategy.
Yes there is a suggestion "box". http://forum.acronis.com/forum/35369 and http://www.acronis.com/support/feedback.html.
This issue has been discussed, but no progress yet on any changes.
Program feature suggestions and program feature changes are only considered if there are enough requests made through these links.
Hi,
I am using True Image 2013 on my desktop with Windows 8 pro (fresh installed )
I make every week a sheduled backup (differential) of my 4 hard disks (on external usb HD) with automatic validation after the back up.
This works fine for 3 of the 4 HD.
The back up of the 4th HD ends normaly ( I can mount it and copy files) but validation fails --> Archive is damaged (error 0x70020) !! [PS : Could not find errorcode in KB]
When I perform a new validation a few hours later, then the validation is ok ("Back up is valid").
This occured always with the same HD (Western Digital 2 TB).
The problem now is : Is that back up really reliable ??
HeGu,
I think someone answered your question in another thread, but if you can mount the image OK, then it can't be damaged, otherwise Windows would not be able to mount it and allow you to access it.