Skip to main content

Exchange 2013 - Backup failed

Thread needs solution

I have a problem with the backup of Exchange 2013 VM (App-aware).
HOST ESXI: 5.5.0 Update 2
VM: Windows Server 2008 R2 / only with Exchange 2013
VMware Tools on VM: Version 9.4.12 build-2627939
Database #1: size of DB = 370GB / size of LOG files = cca. 2GB
Database #2: size of DB = 378GB / size of LOG files = cca. 800GB

On this VM, we have attached iSCSI volumes from NAS (with Microsoft iSCSI connector). There are 2 databases - Database #1 is located on the C:\ drive together with OS (datastore on SAN), and the Database #2 is located on the iSCSI connected volume (on the NAS).
We have VSS Windows backup only for C:\ drive (Database #1) which is doing backup on the another iSCSI volume attached to the VM (the same NAS). Every day this Windows VSS backup of complete drive is performing without problem and the LOG files are truncated after every backup.
For the Database #2 we don´t have any backup and because of that our LOG files is getting bigger and bigger. I cannot do the Windows VSS backup for this database because size of the drive is 2.5 TB - Windows cannot do the backup of drives larger than 2 TB. I want backup it with Acronis so the LOG files will be also truncated.

Here you can find the LOG from Acronis failed backup for our Exchange Server. I have to mentioned, that Acronis App-Aware backup for our Domain Controller with the same OS, VMWare Tools version, on the same ESXI host is performing without the problem...

Task 'exchange backup' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba0950340
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d337
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 537
Module: 149
LineInfo: fc2924f06484b5f1
Fields:
Message: Meta collection during application-aware backup failed.
--------------------
Error code: 239
Module: 83
LineInfo: b7e5b06ccbf4eac0
Fields:
Message: Failed to execute agent 'exchange_backup_agent.exe' with parameters '{ --archive_path, C:\Users\admin\AppData\Local\Temp\A28C32B0-18D2-49AA-BC64-902E281D8B19\msexchange_meta\, --archive_name, msexchange_meta }'.
--------------------
Error code: 240
Module: 83
LineInfo: a83807079d0431a
Fields:
Message: Failed to run script 'cd "C:\Users\admin\AppData\Local\Temp\A28C32B0-18D2-49AA-BC64-902E281D8B19\" && exchange_backup_agent.exe "--archive_path" "C:\\Users\\admin\\AppData\\Local\\Temp\\A28C32B0-18D2-49AA-BC64-902E281D8B19\\msexchange_meta\\" "--archive_name" "msexchange_meta">0F766509-2537-4350-A263-69D7C710B7D5'.
--------------------
Error code: 139
Module: 83
LineInfo: a83807079d04314
Fields: RetCode : 1
Message:
--------------------'.

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

Hi Marin,

First of all note that if you perform a backup of this Exchange VM then the external iSCSI volumes (connected through Microsoft iSCSI initiator) will not be affected by the VMware snapshot and thus won't be put into the backup. See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm… . Assuming the above the only viable use of the VM backup will be in logs truncation functionality. If that's Ok for you then we can investigate the particular issue you've run into.

The error you receive is related to execution of Exchange metadata collection inside the VM. It may be related to the specifics of the Exchange DBs setup (their location on external storage), though it's not completely clear at the moment. You should contact our support team for assistance with this issue - likely we'll need a couple of remote assistance sessions to figure out what might be wrong. Prior to contacting our support team please run "cscript GuestAgent.vbs > out.txt" command inside the VM using the attached .vbs script (save it to some folder in order to run from command prompt) and get the out.txt outputs.

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

Attachment Size
274323-120121.zip 8.58 KB

Everything is solved...

Problem was because one database was not in a good shape... I repair it with ESEUTIL, clear the log files, mount it again in Exchange...

After this, backup & replication with Acronis works...

Tnx for help