Validate Backup

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 4

I have created a backup to a NAS using the network path and credentials and asked the task to validate the backup. The backup completed and validated correctly and I got an email notification of this.

No I try to validate the backup again (just to be sure) and this fails stating that ATI failed to open the backup and it may be corrupted.
--
More information about this error and solutions may be available online in the Acronis Knowledge Base.
To access the online resource manually, enter the event code at: http://kb.acronis.com/errorcode/
Event code: Event code: 0x01E50013+0x01E50018+0x000B041D+0x00040007+0x0000FFF0+0x80070003
--
This seems odd that the backup task can correctly validate the backup but a second attempt fails to find the backup.

Mer, 08/07/2013 - 18:28
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 51
Commenti: 3768

When using ATI with a network drive, use a UNC path to your NAS device for a backup destination, not a typical friendly "mapped" drive. e.g.
\\192.168.2.25\My Backups\

It should also be possible to use a UNC path that includes server name rather than IP, such as
\\server1\My Backups\

ATI will not automatically detect a NAS drive. Once you start typing the destination path (click "Browse", type in the "File name" field), you will be prompted for a username and password. You must use enter the username and password that has permissions to access the NAS share you are saving to.

Many users have had issues with NAS, not because of Acronis but because the router gets overloaded with data throughput and cannot keep a consistent enough connection with the NAS for True Image to image or restore. This could cause your validation issue, especially if other traffic was on the network.

Mer, 08/07/2013 - 18:30
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 4

Yeah Tuttle, I have read this reply many times my friend and that is why I used a UNC path.

Mer, 08/07/2013 - 19:46
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 4

Ok, think I got it... When you specify the destination Synology NAS you MUST use the IP address and not the network device name.

Ven, 08/09/2013 - 15:11
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 4

I would also advise that you remove any mapped drive references to the NAS as this only confuses ATI when you try to validate a previously completed backup. My problem seemed to be that I had a mapped X: drive to the network location so although a backup task completed and validated, any attempt to validate again would result in ATI using the mapped drive reference even though I used the IP address when creating the backup.

ATI used the X: reference to locate the file but failed to actually see the file when starting the validation, resulting in the file not being seen, and as a consequence being logged as corrupt.

Solution: Disconnect the X: drive and remove any reference to it. This means the only root to the NAS is via the network path. Then backup your files/folders to the NAS using the network address and validate any backups from the network address :)

Sab, 08/10/2013 - 09:13