Skip to main content

Backup error after upgrade from V8, Build 8.0.8184 to v9.1.0007

Thread needs solution

After upgrading from V8.0.8184 to V9.1.0007 we notice the following problem:

The backup-tasks are being executed correctly, recoverypoints are correct and contain the correct data. Nevertheless the backup-task reports error.

The last LOG-entrance of the backup reports (all other preceding LOG-entrances of the backup-task are correct):

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

Task 'Backup 05:00 TEMPLATES' fehlgeschlagen: 'Erstellen eines Backups fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 3
Module: 435
Zeileninfo: 555b5abba095034c
Felder: $module : C:\Program Files (x86)\Acronis\vmProtect\Windows Agent\vmms.exe
Nachricht: Erstellen eines Backups fehlgeschlagen.
--------------------
Fehlercode: 1
Module: 437
Zeileninfo: 56ef72df34adb8a3
Felder:
Nachricht: Erstellen eines Desaster-Recovery-Plans fehlgeschlagen.
--------------------
Fehlercode: 4001
Module: 20
Zeileninfo: 665f1f51cfa70f16
Felder: path : C:\Program Files (x86)\Common Files\Acronis\vmProtect\Common\libxslt.dll
Nachricht:
--------------------
Fehlercode: 65520
Module: 0
Zeileninfo: bd28fdbd64edb8bf
Felder: code : 2147942527
Nachricht: Die angegebene Prozedur wurde nicht gefunden
--------------------'.

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

Any ideas how this can be fixed?

Thanks for all suggestions.

Olivier

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Oliver,

The problem here is related to disaster recovery plan creation which failure causes the entire backup task to be marked as failed (even though in fact the backup works fine). In the 9th version there is new set of 3rd party .dlls used for this purpose (libxml2.dll + libxslt.dll for example) and in some cases these .dlls are also registered by other software installed on the machine where you also have Acronis Backup for VMware Windows Agent running. Therefore it causes the wrong .dlls to be loaded and thus fail. The solution here is to enforce loading proper .dlls using the following steps:

1) Stop Acronis vmProtect Managed Machine Service (Start->Run->services.msc)
2) Copy all the .dlls from

C:\Program Files (x86)\Common Files\Acronis\vmProtect\Common\

to

C:\Program Files (x86)\Acronis\vmProtect\Windows Agent\ (change the path to the folder where you installed the Acronis Backup for VMware Windows Agent originally)

3) Start Acronis vmProtect Managed Machine Service

This should do the trick. If not then please contact our support team for assistance with reference to this thread and reference to TTASK-7120 (that's the ID of our internal ticket related to this problem).

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

Hi Vasily

Thank you very much, it worked! Backups are reported as succesfull!

Best regards

Olivier