Aller au contenu principal

Nonstop backup stopped - file is corrupt

Thread needs solution

It appears that the cdp.metadata file is again corrupt. This is becoming a weekly failure. Windows event log shows no disk errors, or errors associated with Acronis. Knowledgebase has no info (similar with most errors reported and searched for). Acronisinfo.exe file is attached. Acronis log file indicates a file is corrupt, but also claims that Nonstop backup has been created successfully. System tray icon disappeared.

I believe if I delete and rebuild NSB, that all version history will again be lost. This should not happen as it renders NSB useless.

Fichier attaché Taille
acronisinfo.zip 7.8 Mo
0 Users found this helpful

Hello Tom, i am also experiencing difficulties with the NSB in the current build of Acronis True Image 2013. May i ask you a few questions:

- Which version of Acronis Backup software are you using?

- What is your target location of the NSB?

  1.  Is the NSB target location on an Internal Drive?
  2. Is the NSB target location on an External Drive, connected through a USB, Firewire or eSATA connection?
  3. Is the NSB target location on an External Network Storage, connected through a wired network adapter?
  4. Is the NSB target location on an External Network Storage, connected through a wireless network adapter?
  • When are you experiencing these problems?
  1.  Directly after the first backup?
  2. After several succesful backups?
  3. After a few weeks?

best regards,

Sven

Sven,

Here are some answers:

- Which version of Acronis Backup software are you using?
TIH2013 & Plus Pack build 5551

- What is your target location of the NSB?
e:\Time Explorer Storage\241185C4-E522-4D87-8E2D-0524472121CB\

Is the NSB target location on an Internal Drive?
No

Is the NSB target location on an External Drive, connected through a USB, Firewire or eSATA connection?
External USB 2.0 hard drive

Is the NSB target location on an External Network Storage, connected through a wired network adapter?
No

Is the NSB target location on an External Network Storage, connected through a wireless network adapter?
No

When are you experiencing these problems?

Directly after the first backup?
NSB was running pretty much okay, but I did have to set its "subsequent failures" properties in services.msc to "restart the service" rather than the default "do nothing"

After several succesful backups?
Yes, NSB was running okay, but I think there is an issue when resuming from sleep mode, which is why I changed the setting above.

After a few weeks?
It ran okay for about a week, then the cdp.metadata file became corrupt.

HTH,

Tom