Skip to main content

Acroinis Backup 11.5 XML file problem

Thread needs solution

Hi everybody!
I'm an IT consultant and I have many customers with Acronis products installed in their networks.
I'm facing an annoying problem that happens in certain circumstances:

- Acronis Backup 11.5 Virtual Edition
- Backup through Virtual Appliances
- Acronis unmanaged centralized vault placed on a QNAP NAS and accessed via CIFS/SMB share

Backup job seems to work fine, but often some VM does not get saved, so after some time of work I found that the XML file that corresponds to the VM name is 0 Byte in size.

First I tried to apply a resolution suggested by Acronis support, so I delete the corrupted XML file and it will start a fresh backup chain.

It is a poor resolution, because it will start a new backup chain every time an XML does get corrupted, so, if I have those files corrupted every day, I must restart my backup chain everyday!

I wrote a VBS script in order to daily backup those XML files and try to restore them in a consistent state when some of them will become corrupted.

It seems that is a pretty good solution, but I cannot do this task every single day, and I want to discover and resolve why those files get corrupted.

I noticed that this behaviour will happen ONLY in the situation described above.

As example, I have a customer that use a QNAP NAS as backup repository mounted to a windows server as iSCSI LUN and accessed by windows share, altough the backup is done in the same way (virtual appliances and unmanaged centralized vault), XML files never get corrupted.

Another customer uses centralized MANAGED vault on a QNAP NAS accessed by CIFS/SMB, but the backup jobs are done via local agent installation (this is a XEN server environment) and also in this environment XML files does not get corrupted.

I'm out of ideas...

Does anyone had the same problem?

Thanx a lot to everybody in advance!

0 Users found this helpful

Hello Metalgalle,

according to our experts disabling OPLOCKs on NAS might be helpful but it is not a 100% solution.

Such issues need to be investigated in particular environment and I would recommend you to contact our support.

Thank you.