Validation: separated Vs together backup
The validation performed together backup fails while the validation performed separately (that is after the backup is finished) succeed: why??
What's the difference between the validation executed with the backup and that done later?
And how can I discover what's the cause of the validation failure? (detail, error code, etc..)
Is Acronis investigating on it?
And what to do in these cases? When the process fails you're not sure the backup is good in case of restore.. so have I to abandon ATI as backup system??
Where is the backup being stored? Is it a network disk? Be sure the storage device is not timeout out by going to sleep.
Boot from the user created TI Recovery CD and perform a validation via the CD.
If validation successful, a restore should be successful.
You might also want to consider a disk check for disk or file errors.
Validation is not a check of your data but an assurance that the disk has been read and written to successfully.
Posting on the forum is not notifying them of an issue. You may want contact them via Live Chat or email.
Instructions are along left margin or support via upper right corner.
I use many storages to backup my computer: 1 network disk and 3-4 USB disks.
It seems like on network disk the backup+validation always succeeds (3/3). On USB disks it depends, sometimes it succeeds sometimes not, moreover on one of them: I'm doing many backup+validation to get stats and understand if and which disk could be affected..
However it's so strange that from a certain day on, the validation has started to fail, even if all my USB disk are good (performed check disk and diagnostic tool on all of them).
As already discussed, it's not good that ATI bootable CD doesn't give detail on validation error: why can it say the reason, for example "just failed at the beginning of the validation because the backup file is locked".. etc..?
Validation will also fail if the usb device has been assigned a differing drive letter than original task assignment.
Here are some options which involve USB and sleeping.
Open Device Manager.
1. Look under the Disk DRives for any usb drives. If found, click under policies and select Quick Removal. Remember this is for usb devices only.
2. Look under Universal SErial Bus controllers
Look under ALL with the word hub
Right click on each hub listing
Under Power Management, be sure ALL options is NOT CHECKED which read
Allow the computer to turn off the device to save powoer.
Close Device Manager
Open Control panel Power options
Locate and select the power plan in use
Click Change Plan settings
Click "change advanced power settings"
Under USB settings
Disable Selective Suspend
Save changes
[quote=GroverH]
Validation will also fail if the usb device has been assigned a differing drive letter than original task assignment.
Here are some options which involve USB and sleeping.
What do you mean?
Maybe that if I connect my (destination) USB storage to my computer and it's the unit "F:" and during backup it's a different letter ("K:") this'll cause the validation failure?
Open Device Manager.
1. Look under the Disk DRives for any usb drives. If found, click under policies and select Quick Removal. Remember this is for usb devices only.2. Look under Universal SErial Bus controllers
Look under ALL with the word hub
Right click on each hub listing
Under Power Management, be sure ALL options is NOT CHECKED which read
Allow the computer to turn off the device to save powoer.Close Device Manager
Open Control panel Power options
Locate and select the power plan in use
Click Change Plan settings
Click "change advanced power settings"
Under USB settings
Disable Selective Suspend
Save changes
I tried to set the USB settings as you told me but the validation still fails.
What do you mean?
Maybe that if I connect my (destination) USB storage to my computer and it's the unit "F:" and during backup it's a different letter ("K:") this'll cause the validation failure?
During an attempted backup, if the destination is a different drive letter than original task creation, the backup will fail and will not begin. Destination drive letter must always be the same as drive letter originally assigned If destination drive letter has changed, a task MOVE option must be invoked to change the orignal drive letter destination to the new drive letter destination.
When validation a backup, all backup associated with the task should be present and in the same folder.
This is the summary of my backup:
Operations
Number of operations: 5
1. Creating partition image
Hard disk: 2
Drive letter: G:
File system: NTFS
Volume label:
Size: 350Mb
1. Creating partition image
Hard disk: 2
Drive letter: C:
File system: NTFS
Volume label: MYSELF-PC-PROG
Size: 232.5Gb
3. Creating partition image
Hard disk: 3
Drive letter: D:
Filem system: NTFS
Volume label: MYSELF-PC-DATA
Size: 1,819Tb
4. Saving partition structure
Hard disk: 2
5. Saving partition structure
Hard disk: 3
BACKUP METHOD: incremental
COMPRESSION LEVEL: Maximum
ARCHIVE VALIDATION: validate backup archive when it is created
Do you think that these settings could have problems?