Exchange Aware Backup not working

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 0

Hello,

since last month ive got the Problem, that our Backup for our Exchange Server 2010 Ver.: 14.03.0224.002 on Windows Server 2008 R2 Standard SP1 Fails with the Option "Exchange Aware Backup" with vmProtect 8, Build 8.0.8184.
The VM Runs on a VMWare ESXI 5.1.0, 799733.

In vSphere Client i can see in log that vmProtect is logging in with the Account and creates a Snapshot (it Needs about 1 and Shows in vmProtect 5% Progress) . 2 minutes later it jumps to 96% progess and delets the snapshot. After 10 seconds it Shows 100% and the snapshot takes about 1hour to delete).

What i have done so far:
Checked the eventlog -> seems OK to me.
Checked VSSWriters over vssadmin list writers -> All OK
The Windows Server Backup is running without any Problems.
Restartet the VM and reinstalled VMWare Tools.
I allready reinstalled the vmProtect Appliance.
Storage on C: Partition is 29GB free and on D: 95,8GB

Error Log:
Task 'Backup zu 'Netzwerk'' fehlgeschlagen: 'Erstellen eines Backups fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 3
Module: 435
Zeileninfo: 555b5abba09501ce
Felder:
Nachricht: Erstellen eines Backups fehlgeschlagen.
--------------------
Fehlercode: 32786
Module: 114
Zeileninfo: 28314c961de7d32e
Felder:
Nachricht: Vorbereitung auf das Backup fehlgeschlagen.
--------------------
Fehlercode: 353
Module: 149
Zeileninfo: a71592046cb2c5f6
Felder:
Nachricht: Backup der Gruppe fehlgeschlagen.
--------------------
Fehlercode: 2
Module: 218
Zeileninfo: 338a407ad20e0987
Felder:
Nachricht: Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
--------------------
Fehlercode: 368
Module: 149
Zeileninfo: 4db9605401c15283
Felder:
Nachricht: Vorbereitung zur Validierung der Microsoft Exchange-Datenbank fehlgeschlagen.
--------------------
Fehlercode: 358
Module: 149
Zeileninfo: 8e1d384601b2ab4b
Felder:
Nachricht: Die VSS-Metadaten fehlen oder sind beschädigt.
--------------------
Fehlercode: 13
Module: 4
Zeileninfo: 86137b9d60c180c7
Felder:
Nachricht: Die Datei ist beschädigt.
--------------------'.

Any suggestions about to fix this?

Thanks

Thu, 05/07/2015 - 14:40
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Michael,

There was such problem when VM is running on ESXi 5.1 and 8184 build of Acronis vmProtect is used (internal issue ID: TTASK-6551). This problem has been fixed in the 9th version (now called Acronis Backup for VMware), so it makes sense to upgrade to the new version and re-try the operation. To confirm that it works you can try the trial version first (install it as a separate appliance).

Another possible reason is that there is no VMware Snapshot Provider present in COM+ components inside the backed up VM which means that VSS is not properly utilized while creating quiesced snapshot. Re-installation of VMware tools should help in this case.

Also check https://kb.acronis.com/content/31347 which describes typical pre-requisites and possible solutions for VSS-related issues. The following conditions must be true for successful application-aware backup:

1) disk.EnableUUID is set to "true" in VM properties
2) VM does not use IDE disks or dynamic disks (LDM)
3) After creation of quiesced snapshot of the VM (quiesced = on, memory = off) there is a valid vss_manifest***.zip output generated in the VM folder which contains backup.xml + writerX.xml with the description of the VSS writers outputs. An indication of VSS malfunction is presense of only backup.xml in the vss_manifest***.zip without writerX.xml files.

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

Fri, 05/08/2015 - 08:16
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.