In Backup Exec 2010, an Agent for Vmware Virtual Infrastructure (AVVI) 2010 backup fails with the error - Unable to create a snapshot of the virtual machine. The virtual machine may be too busy to quiesce to take the snapshot.

Article:TECH129070  |  Created: 2010-01-22  |  Updated: 2011-04-14  |  Article URL http://www.symantec.com/docs/TECH129070
Article Type
Technical Solution


Subject

Issue



In Backup Exec 2010, an Agent for Vmware Virtual Infrastructure (AVVI) 2010 backup fails with the error 0xe0009574 - Unable to create a snapshot of the virtual machine. The virtual machine may be too busy to quiesce to take the snapshot.


Error



0xe00095a8 - The operation failed because the virtual center or ESX server reported that the virtual machine is busy.

V-79-57344-65304 - The Virtual Machine resource is not responding. Backup set canceled.
Remote Agent not detected on .


Cause



In Backup Exec 2010, an Agent for Vmware Virtual Infrastructure (AVVI) 2010 backup of some Virtual machines fails with the above mentioned error while creating a snapshot of the virtual machine (VM) in question.
 
SYMPTOM:
 
1) Snapshots of the Virtual Machine(VM) in question can be created via the Vmware Vsphere Client User Interface
 
2) Quiescing the VM in question using the VMWare Vsphere API CreateSnapshot_Task fails with the same error "Protocol error from VMX.".
 
The method CreateSnapshot_Task invocation for the Virtual Machine Managed Object fails only when the parameters memory and quiesce are passed as "true".
 
Please check the Vmware Documentation("SDK Managed Object Browser" http://kb.vmware.com/kb/568529) to find out how to access the Managed Object Browser to invoke operations on Vmware Managed Objects.
 
3) Backup Exec Remote Agent(beremote) Debug log on the Media Server shows the following errors:
 
SymVmTools: WaitForTaskComplete: Another task is already in progress.
 
SymVmTools: WaitForTaskComplete: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
SymVmTools: WaitForTaskProc: Thread terminating r=36
 
SymVmTools: CreateSnapshot(2): SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
SymVmTools: CreateSnapshot(1): SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
vddkCreateVMWareSnapshot(): vmcCreateSnapshot failed, result = 0X24
 
vddkCreateVMWareSnapshot(): vmcCreateSnapshot reported: Another task is already in progress.
 

 
SymVmTools: WaitForTaskComplete: reached Error!
 
SymVmTools: WaitForTaskComplete: A general system error occurred: Protocol error from VMX.
 
SymVmTools: WaitForTaskComplete: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
SymVmTools: WaitForTaskProc: Thread terminating r=36
 
SymVmTools: CreateSnapshot(2): SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
SymVmTools: CreateSnapshot(1): SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
 
vddkCreateVMWareSnapshot(): vmcCreateSnapshot failed, result = 0X24
 
vddkCreateVMWareSnapshot(): vmcCreateSnapshot reported: A general system error occurred: Protocol
 

Solution



The Vmware Knowledge base Article "Protocol error from VMX returned when backing up virtual machines"  http://kb.vmware.com/kb/1007346 may be followed to resolve this issue.
 
If any of the above symptoms described above continue to persist, please contact Vmware.
 

Supplemental Materials

ValueV-79-57344-38260
Description

Unable to create a snapshot of the virtual machine. The virtual machine may be too busy to quiesce to take the snapshot.


ValueV-79-57344-38312
Description

The operation failed because the virtual center or ESX server reported that the virtual machine is busy.


Legacy ID



351262


Article URL http://www.symantec.com/docs/TECH129070


Terms of use for this information are found in Legal Notices