Skip to main content

Errors in logfile after successful backup

Thread needs solution

Hello,

after our last backup run we have read the logfile for the task for the first time completly. we have noticed that there are warnings/Errors for some vm's. sometimes it is

--------------------
Fehlercode: 46
Module: 7
Zeileninfo: a5695862aaf8e75e
Felder: PartitionId : 331
Nachricht: Erzwungener Sektor-für-Sektor-Modus.
--------------------
Fehlercode: 37
Module: 7
Zeileninfo: 89d94b01b483de63
Felder:
Nachricht: Index ist beschädigt.

for other vm's the error is

--------------------
Fehlercode: 46
Module: 7
Zeileninfo: a5695862aaf8e75e
Felder: PartitionId : 221
Nachricht: Erzwungener Sektor-für-Sektor-Modus.
--------------------
Fehlercode: 24
Module: 7
Zeileninfo: ef8b1618a4c0dd9c
Felder:
Nachricht: MFT-Bitmap ist beschädigt.
--------------------

These Errors can be right because we have had a san Problem a couple of months ago.
but what it makes strange is that chkdsk cannot find any Problems and that one time the log said "MFT-Bitmap ist beschädigt" (Laga_Sicherung_MFT.txt) and one time "Index ist beschädigt" (Laga_Sicherung_Index.txt) for the same vm.
Are These Errors really correct or is there a bug in vmprotect or somewhere else ?

Sincerely yours

Sven

Attachment Size
laga_sicherung_index.txt 3.93 KB
laga_sicherung_mft.txt 4.83 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Sven,

These messages basically indicate that backup went to sector-by-sector mode either due to file system errors (can be revealed by checkdisk) or conflict with some of the guest VSS writers. You can check the details and possible workaround here: http://kb.acronis.com/content/36993

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager