This article lists possible causes and solutions This article applies to: • Acronis vmProtect 7 • Acronis vmProtect 8 • Acronis Backup for VMware 9 (Acronis vmProtect 9) Symptoms Exchange-aware backup fails with the following error in the log: 16 Error 1/13/12 5:19:25 PM Failed to prepare for the Microsoft Exchange database validation. Additional info: -------------------- Error code: 368 Module: 149 LineInfo: 4db9605401c151e5 Fields: Message: Failed to prepare for the Microsoft Exchange database validation. Additionally, the processing of parameters in a HTML close tag may cause the Microsoft Exchange Information Store service to crash. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem. Only apply it to systems that are experiencing this specific problem. -------------------- Error code: 358 Module: 149 LineInfo: 4db96b Fields: Message: VSS metadata is missing or corrupt. -------------------- Error code: 1001 Module: 460 LineInfo: df98e120ab10cc45 Fields: Message: Failed to parse MsExchange VSS writer metadata. -------------------- Error code: 1003 Module: 460 LineInfo: df98e120ab10cc2d Fields: Message: Expected XML tag not found: WRITER_COMPONENTS OR with the following log. For this specific error. Note the bolded line: Task 'Exchange' failed: 'Failed to create a backup. Additional info: -------------------- Error code: 3 Module: 435 LineInfo: 555b5abba09501ab Fields: Message: Failed to create a backup. -------------------- Error code: 32786 Module: 114 LineInfo: 28314c961de7d3ba Fields: Message: Failed to prepare for backing up. -------------------- Error code: 353 Module: 149 LineInfo: a71592046cb2c5f3 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: 367 Module: 149 LineInfo: 9351a3 Fields: command: --check-env Message: The agent on the guest system has failed to process the request. -------------------- Error code: 1 Module: 470 LineInfo: dd1e7a681d3fe6a8 Fields: $module: C: DOCUME~1 ADMINI~1 LOCALS~1 Temp 1995738C-A9A9-4B1F-ADBE-5C7E2D8A98EE exchange_backup_agent.exe Message: Failed to process command 'CheckEnvironment'. -------------------- Error code: 25 Module: 470 LineInfo: 4345d9 Fields: Message: The VSS components of VMware Tools are corrupted or not installed. Cause There are several possible causes. Please look through the Solution section of the article. Solution • If you are running Microsoft Exchange on Windows 2008-based machine in ESX(i) 4.1 or higher environment then please ensure that disk.EnableUUID parameter is present in the Exchange VM configuration. For detailed instructions please see VMware KB:. • Exchange-aware backup is not possible if Microsoft Exchange is installed on Windows 2003 SBS edition without additional adjustments. By default, the Setup program for Microsoft Windows Small Business Server 2003 turns off the Microsoft Exchange Server 2003 writer for the Volume Shadow Copy service. To protect data using Acronis vmProtect 7, the Exchange 2003 writer must be turned on: See Microsoft TechNet:. For Exchange 2007/2010 versions the VSS writer is turned on by default, so these versions are not affected by this issue. This is a by-design behavior. • This solution applies to ESX(i) 5.0 and older. This solution applies only if you have the The VSS components of VMware Tools are corrupted or not installed error message. The VMware Snapshot Provider service is required for proper application level quiescing. The solution is to register the necessary COM component manually as described in VMware KB:. To ensure the proper registration of VMware Snapshot Provider COM component use the following command for registration which sends the log output into a file: 'C: Program Files VMware VMware Tools COMREG.EXE' -register 'C: Program Files VMware VMware Tools Drivers vss VCBSnapshotProvider.dll' 'VMware Snapshot Provider' 'vmvss' 'VMware Snapshot Provider' > C: register.log 2>&1. Exchange Event Id ListThe successful log will look similar to the following: Couldn't find application to unregister: VMware Snapshot Provider Creating new COM+ application (VMware Snapshot Provider). Setting application options. Creating the service. Registering the DLL. Securing the application. Searching for admin group using WMI. Searching for LocalSystem account using WMI. Granting new role to LocalSystem user. • In case the VMware tools were installed on the Exchange VM in non-interactive (silent) mode the VSS modules may not be registered properly. The solution in this case would be to re-install VMware tools in interactive mode by logging into VM and performing the installation of the VMware tools. • In case there is User Account Control enabled inside the VM running Microsoft Exchange, make sure you have installed the Exchange Backup Agent prior to running Exchange-aware backup of this VM. It can be extracted from Acronis Backup for VMware (former vmProtect) installation package: look for 'Acronis Backup for VMware Backup Agent' component. • If nothing of the above helps then the most probable reason is incorrect vss_manifests***.zip archive generated while quiescing the Exchange VM, i.e. It is not generating proper VSS manifest output. Please ensure that your VM meets all prerequisites imposed by VMware for Application-consistent quiescing which depend on vSphere version and the Guest OS type. For example Windows 2008 installed on IDE disks in vSphere 4.1+ environment doesn't support Application-consistent quiescing. Application-consistent quiescing is required to get non-empty VSS manifests.zip output: See the following. Microsoft Exchange Server Event Id 1000 Vmware ToolsWhen creating a quiesced snapshot of the VM from vSphere Client interface there must be vss_manifests***.zip file generated on the datastore in the folder where this VM is: Under normal circumstances the VSS manifests.zip file is not empty, however if there are some problems with the VMware tools then the outputs may be corrupted even though the VM meets the requirements for Application-consistent quiescing, which means that VMware tools need to be re-installed. • If re-installation of VMware tools or other suggestions above does not help then please collect the following information after creation of the quiesced snapshot of the Exchange VM and with the following diagnostic information: • Outputs of the vssadmin list writers command from the guest OS (Exchange VM) in to check that there are no failing VSS writers. See; • Windows System Information from the guest OS (Exchange VM): Start -> Run -> msinfo32 -> Save to File • Windows Event Logs from the guest OS (Exchange VM): Start -> Run -> eventvwr.msc. Both System and Application logs are required. • The vss_manifests***.zip file obtained in step 6 of the above described steps. More information See also. Error Event Id 1000Tags: • • • • •.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |