Skip to main content

backup on tape failed - which is the relevant issue in the error log?

Thread needs solution

Hello,

I have three DLT 6 tapes rotating, making three generations of tape backups once a week.

The last backup failed with the following log. The error code wasn't found in the Acronis db (neither 41, nore the event code 0x01330029+0x01490002+0x01350016+0x01490003+0x00010424+0x00070004+0x00400005+0x00430074+0x00040007+0x0000FFF0+0x80070002). How are these error logs to be read? Is the initial error the top most or the bottom most? The top most "Command failed" - but which command? Or the bottom most "The system cannot find the specified file" - which file??? 

Afterwords I tried to scan and inventory the tape, both jobs start but stay at 0% without any error and without coming to an end.

Any ideas how to find, what is going wrong here?

Thank you

***************************************************************************

Error log:

Ausführen des Befehls fehlgeschlagen.

Zusätzliche Info:

--------------------

Fehlercode: 41

Module: 307

Zeileninfo: e6792a5ee190dda6

Felder:  $module : agent_protection_addon_vs_43916

Nachricht: Ausführen des Befehls fehlgeschlagen.

--------------------

Fehlercode: 3

Module: 329

Zeileninfo: 1cd98aae889424f9

Felder:  $module : disk_bundle_vs_43916

Nachricht: Backup ist fehlgeschlagen.

--------------------

Fehlercode: 1060

Module: 1

Zeileninfo: b43e776571144dee

Felder:  $module : disk_bundle_vs_43916

Nachricht: Ausführen der Aktionen fehlgeschlagen.

--------------------

Fehlercode: 4

Module: 7

Zeileninfo: 9d2de1f088cbc58b

Felder:  $module : disk_bundle_vs_43916

Nachricht: Schreibfehler.

--------------------

Fehlercode: 5

Module: 64

Zeileninfo: 6c55082b07095929

Felder:  $module : disk_bundle_vs_43916

Nachricht: Öffnen des Archivs zum Lesen und Schreiben mit wahlfreiem Zugriff fehlgeschlagen.

--------------------

Fehlercode: 116

Module: 67

Zeileninfo: ba1336035c2a6275

Felder:  id : E5EA60AE-5000-474C-82A1-F87B6DFE682A, barcode : , label : Band 2, $module : disk_bundle_vs_43916

Nachricht: Die Informationen auf dem Band 'Band 2' wurden möglicherweise geändert. Sie sollten das Band neu scannen.

--------------------

Fehlercode: 7

Module: 4

Zeileninfo: c41defba28f4d01e

Felder:  $module : disk_bundle_vs_43916

Nachricht: Fehler beim Öffnen der Datei.

--------------------

Fehlercode: 65520

Module: 0

Zeileninfo: bd28fdbd64edb8ee

Felder:  code : 2147942402, $module : disk_bundle_vs_43916

Nachricht: The system cannot find the file specified

--------------------

Acronis Knowledge Base: http://kb.acronis.com/errorcode

 

Ereignis-Code: 0x01330029+0x01490002+0x01350016+0x01490003+0x00010424+0x00070004+0x00400005+0x00430074+0x00040007+0x0000FFF0+0x80070002

0 Users found this helpful

Hello Tiemo,

The errors are hierarchical, meaning that the top error message in the log error stack comes from the highest placed component. Usually this is the backup task itself and it will say something not very useful, like "backup failed". However, this failure was caused by some smaller part of the backup task, which is the next error you see. This continues until the specific (usually) very small component is reached.

So in your example, you get that the backup failed because a sub command failed. This sub-command is a write operation that failed because we couldn't open the archive because the product found something unexpected on the second tape. Specifically, we could open some sort of data because "The system cannot find the file specified".

The final is actually a Microsoft error, which tells me we tried using a Windows API to open something related to tape 2 and Windows could find the file our product was asking for. This probably means that the tape database on disk is not synchronized with the contents of the tape.

This chain of errors was originally designed this way because it gives a good snapshot of what the product was doing in the different modules at the time the error happened, but does make for more complex troubleshooting if you don't have experience with the errors.

So, generally, you want to look at the very last error message in the error stack for the true cause of the different problems and start going up the stack to find as much context for the error as possible. 

As for the solution to this issue: I would suggest following the instructions in the message here: Sie sollten das Band neu scannen.

 

Hello Igor,

thank you for your helpful explanations.

After that error, I first tried to scan the tape, but the job just stayed at 0%, nothing happened and never came to an end, until I quit it after 10 minutes. The same happened when I tried to inventory it.

Any other ideas, what I could check?

Thanks

Tiemo

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hi all, 

The issue is already being investigated within a support-ticket. It seems to be due to incorrect initialisation in Windows Device management.

Thank you,