Nonstop backup error events 0x001703EE, 0x00170803, and 0x006B0000
Nonstop backup appears to work fine for a couple of days, then stops. Clicking "Recover" displays a message "There are no versions of the backup." The event log (codes in title) says "Read error or metadata content is corrupted.", "Consolidation failed." , and "Operation aborted." There is nothing in the knowledge base about any of these errors.
In this state, the nonstop backup cannot be restarted; it must be deleted and recreated. It runs fine for a while and then dies as described above. Any ideas about what to do?
Thanks.
- Log in to post comments
Thanks for the reply, Colin. I'm running Windows 7 Ultimate 64bit. It appears the Windows defragger has been running every Wednesday at 1:00 AM (I just turned it off). Also System Mechanic was doing this automatically (I just turned it off). I've recreated the nonstop backup (it died again). I'll let you know how it does. Are there any other things I should be looking for?
- Log in to post comments
Mark,
You might want to run chkdsk /f or r just to make sure there is no sector corruption on the disk.
- Log in to post comments
Hi,
Without trying to hijack Mark's thread, I was going to make a very similar post to the forum. Like Mark, my Nonstop backup runs for several days then stops (with little announcement) showing in the logs that a "Read error or metadata content is corrupted". If I didn't check within Acronis and it's logs I wouldn't know that the non-stop backup had failed.
My setup (purely to understand if this is similar to Mark) is a Windows 7 Professional x64 machine (latest MS patches etc), Acronis 2013 (Build 5551), Dell Latitude E6420 Laptop, Freecom Toughdrive USB2 1TB drive. The Freecom drive is connected to the USB port on the Dell docking station.
I've got the Freecom drive as the target and currently this is a dedicated Acronis Secure Zone, although previously I've tried it has a regular disk with the same results.
Like Mark, the only "cure" I can find is to delete the non-stop and recreate it, but after a number of days the failure will occur again.
I'd be interested to understand if this is similar to Mark.
Thanks
Iain.
- Log in to post comments
Thanks for joining in, Iain. It sounds like we're experiencing the same thing.
Unfortunately, even after turning off disk defragging the problem persists: after about 2 days, the backup fails. Chkdsk on the source drive comes up clean. So what else might be interfering?
I had been using a brand new eSata drive solely for this purpose but now I'm trying to back up to one of my network drives instead. We'll see if that makes a difference. Already I've noticed something different: Windows Explorer shows the backup folder and file -- and lets me explore the contents; none of this was true with the eSata drive, which merely showed the space consumed.
For the next release, it'd be nice if:
* the error messages in the log were a bit more descriptive (or if the referenced KB pages actually existed).
* the backup fails more gracefully so we might recover data from it.
* we could restart the backup without having to delete the current task and rebuild it from scratch.
Thanks, all.
Mark
- Log in to post comments
NSB has been the same for some time - when it stops the only way out is delete & recreate. It really is incorrectly named. NON STOP has been an industry buzz word for the last 30 or more years. NSB does not in any way fulfil that function. If your disk fills up there does not seem to be any automatic clean-up function to make space. It also appears difficult on some occasions to remove old data manually. If the system shuts down under certain conditions it would also appear that NSB can be corrupted.
The only thing I can say is that so far NSB means you have a NON STOP battle to keep it working and invariably you loose and have to start again.
Still waiting for a version that actually fulfils its description - NON STOP means start now and run forever.
- Log in to post comments
Thanks Ray. At the rate I'm going, though, there's little chance I'll ever get close to filling up my destination disk!
Mark
- Log in to post comments
Well, the results of my trial are in: non-stop backup to the network drive fails after about the same amount of time as to the eSata drive. There is a difference, though: the backup is recoverable. However, you still can't restart it.
- Log in to post comments
the same problem ocures to my nonstop backup.
running windows 7 64 professional. no diskutils running, did chkdsk /f
have sata system (250 GB) and backup (2TB) disks
the nonstop backup has worked fine but now starts becoming uncomfortable.
normal partion backup functions OK
attached log
| Attachment | Size |
|---|---|
| 138390-109435.jpg | 122.21 KB |
- Log in to post comments