Backup of 20GB VM and 1TB Raw Mapped Lun snapshot issues

[durandl]

We are having an issue with a backup of 20GB VM and 1TB Raw Mapped Lun. Sometimes the backup will not be able to remove the snapshot causing an error in vSphere, disconnecting the host. When trying to reconnect the host, we see the following error:

A general system error occurred: internal error:
vmodl.fault.HostCommunication

Has anyone seen this error or knows a way to fix this?

[Gostev]

Hi, might be best to open support case with VMware on this and have them review ESX host log files for clues...

[durandl]

Hi Gostev,
I have and they told me it was due to the backup software and snapshot creation/deletion.

[durandl]

This is the error I get after a successful backup:

Removing snapshot
RemoveSnapshot failed, snapshotRef "544-snapshot-33", timeout "3600000"
Unable to access file <unspecified filename> since it is locked
Veeam Backup will attempt to remove snapshot during the next job cycle, but you may consider removing snapshot manually.
Possible causes for snapshot removal failure:
- Network connectivity issue, or vCenter Server is too busy to serve the request
- ESX host was unable to process snapshot removal request in a timely manner
- Snapshot was already removed by another application

[durandl]

This is the error in vSphere on the orphaned client:

Remove snapshot
<SERVERNAME>
Unable to
access file <
unspecified
filename>
since it is
locked
root
2/21/2011 9:58:06 AM
2/21/2011 9:58:06 AM
2/21/2011 9:59:25 AM

[Gostev]

Unable to access file unspecified filename since it is locked

This issue is known, and does not exist in the current version of the product. Please search forum for the error above for more information and immediate resolution. I do recommend upgrading to the latest version of the product even though you can resolve this manually. Thanks.

[durandl]

What is the newest version? I have 5.0.1.198 (64bit)

[Gostev]

Yes, 5.0.1 is the one that should not have this issue.

[durandl]

well... it does. I would like to get this taken care of soon Any ideas?

[Gostev]

Other users have not reported this with 5.0.1, so this must be specific to something within your environment.
As always, best idea with any technical issue is to contact our support directly.

[durandl]

I have created a case. Just hoping to get some info while I wait for a call back.

[melvinhare]

Hi

Just wondered if you'd resolved this issue ?