Nonstop backup stops!

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

I am using ATIH 2012 build 6163 on a Windows 7 Professional x64, and cannot get the nonstop backup to keep running. After starting it, it runs for a few minutes and then the systray icon simply says it has stopped. No explanation in the gui.

I am using the secure zone for backup destination, and after browsing the forums I have also tried reducing the size of the ASZ to something like 95 GB, but without improvement. I have only selected a few of the most important top-level directories (dedicated software development directories, users-folder, etc.) to include in the nonstop backup, but still the problem persists.

When looking in the afcdpsrv.log file I find something like several thousands of lines like these (all identical):

14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.

As far as I can see, the logfile does not mention what file it is having problems reading. How useful is that?

After a long run of lines like the above, it finally boils down to this:

14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: Code: 0x170803 tag: 0xBE4A335CC601F5FB message: Operation has been aborted. Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: tid=0x000013E0>ArchiveApi::Operation::Execute returned error:
14:10:14: Code: 0x170803 tag: 0xBE4A335CC601F5FB message: Operation has been aborted. Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: tid=0x000013E0>Archive existence checked after full backup with result: true
14:10:14: tid=0x000013E0>Full backup complete
14:10:14: Code: 0x1720001 tag: 0x6F3D13FF1B3C092D Code: 0x1720001 tag: 0x6F3D13FF1B3C06D0 Code: 0x1D tag: 0xB436A436FE785903 Code: 0x170803 tag: 0xBE4A335CC601F5FB message: Operation has been aborted. Code: 0x1703ED tag: 0x846A5A7F70BD3AC4 message: Write error. Code: 0x40002 tag: 0xD18A9C757EF132F0 message: The end of the file has been reached.
14:10:14: tid=0x000013E0>Archive existence checked with result: true
14:10:14: tid=0x000013E0>globalOperationMutex Unlock()
14:10:14: tid=0x000013E0>Stop session 00000004 status 0x0
14:10:14: tid=0x000013E0>Driver session C: stopped with status 0x0
14:10:14: tid=0x000013E0>Delete session 00000004 status 0x0
14:10:14: tid=0x000013E0>Session destruction, kernel handle 00000000
14:10:14: tid=0x000013E0>Session fail stop count: 9
14:10:14: Nonstop backup has been created successfully.

And then the logfile stops, as well as the nonstop-backup itself.

Any idea how to get this working other than randomly deselecting directories included in the nonstop backup and trying until it keeps running? It would take ages, and what is the use of a nonstop backup if some mysterious files cannot be included in the backup (you can bet that those files are probably the ones you would need to restore). I am taking regular image backups also, but would like the fine grained nonstop backup when doing software development.

Sun, 11/27/2011 - 13:52
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 8

Sad but true ! I got so many problems with this product that is unbelievable: it took 3 weeks to activate the product and make it work; after just few days another problem: Failed to deploy task. scheduling service is off.
I try to contact the live support and the website tells me that the online support is expired and I have to pay if I want it!
I have only used it one week !
Terrible customer support !
Do not waste your time with this product !

Wed, 11/30/2011 - 05:43
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello krisku and Angelo,

Thank you for your comments.

krisku, let me help you with this issue please. I would recommend to recreate your Nonstop backup, it is very likely that the issue will be fixed.

If you continue to experience difficulties, I would recommend to collect this report and contact our Support team directly.

Angelo, we really appreciate your feedback. I have replied to a similar post that you made in another thread here.

Please let me know if you have additional questions.

Thank you.

Thu, 12/01/2011 - 12:47
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
Posts: 0
Comments: 1

I have the same problem, NonStop 2012 (6163) just stops. I am backing up to a home NAS connected as "\\nas name\nas private directories\myname\AcronisBackups" over 100baseT ethernet...

any attempt to restart it causes it to run for a couple minutes, then goes back to stop. the backup version increment doesn't change. there's no errors in the log.

gads, saved logs are in XML ? meh. the log shows ...

* operation nonstop backup started
* updating backup database: setting verification requirement for database access.
* creating incremental backup archive
.....
* operation has succeeded

if I click the 'recover' button, it just sits there with a blank popup with a grey spinner.

Thu, 12/01/2011 - 19:30