Quantcast
Channel: VMware Communities : Blog List - All Communities
Viewing all articles
Browse latest Browse all 3135

Backup solutions fail to backup a virtual machine after vMotion

$
0
0

 

In the Avamar Administrator interface a Virtual Machine is labeled with its VMX file location instead of

 

its VM name (000485609)

 

Avamar Client for VMware

 

 

Issue: The VM name is displayed incorrectly for random VMs on the Avamar GUI.

 

The VM name can be seen similar to:

 

"%2fvmfs%2fvolumes%2f5124e1c8-f4fd5839-7764-b8ac6f8a9883%2fpoi%2fpoi1.vmx"

 

In vpxd log file, you see many references to VmRemovedEvent and VMRenamedEvent:

 

grep "Invalid host event" vpxd-*.log | grep "vim.event.VmRenamedEvent"
grep "Invalid host event" vpxd-*.log | grep "vim.event.VmRemovedEvent"

Resolution

 

Currently, there is no resolution.

VMware is aware of this issue and is co-working with Backup solution teams to provide a solution.

To work around the issue, use these options:

  • Avoid vMotion for the backed up virtual machines.
  • Correct the backup set when necessary.
  • KB (2148378)

 


Viewing all articles
Browse latest Browse all 3135

Trending Articles