VMware Cloud Community
azlans27
Enthusiast
Enthusiast
Jump to solution

Failed to Backup VM - Failed to retrieve next FILE_PUT message

Hi All,

I just got problem in my environment. Here it is:

Before, the VM was backup normally during last 1 year. But, last week, the backup was failed. Here is failed notification:

Processing SERVER-A (1xx.1xx) Error: DiskLib error: [4].Success Failed to retrieve next FILE_PUT message. File path: [[datastore_name] SERVER-A/SERVER-A.vmx]. File pointer: [0]. File size: [3338].



My Environment Info:

VM Os               : Windows Server 2003

VMware Esxi      : 5.5

Vcenter Version  : 6.0

Backup App        : Veeam B&R


Additional Information : backup job for other VM's run normally


Why this error happen? What to do to fix this issue?


any suggestion will be appreciated.


Best Regards,

Azlan Syah


1 Solution

Accepted Solutions
azlans27
Enthusiast
Enthusiast
Jump to solution

after hours of tshooting, I already fixed issue above.

Here it is what I do:

1. You should know the datastore where VM was stored.

2. Remove VM from inventory

3. Create new VM as usual. But instead of creating new VMDK disk, we should choose 'use existing disk'. So, choose previous VMDK file. Then follow the wizard till the end.

Here is the link for reference about this case:

VM Still Working Despite Being Powered Off | Jordansphere

View solution in original post

Reply
0 Kudos
3 Replies
azlans27
Enthusiast
Enthusiast
Jump to solution

after hours of tshooting, I already fixed issue above.

Here it is what I do:

1. You should know the datastore where VM was stored.

2. Remove VM from inventory

3. Create new VM as usual. But instead of creating new VMDK disk, we should choose 'use existing disk'. So, choose previous VMDK file. Then follow the wizard till the end.

Here is the link for reference about this case:

VM Still Working Despite Being Powered Off | Jordansphere

Reply
0 Kudos
TomLong1
Contributor
Contributor
Jump to solution

As an aside; I was having this problem over the last couple of days. I vMotioned the server to another host and retried the Veeam backup and it succeeded. Might be a little less effort than rebuilding the VM from the VMDK.

HWillenborg
Contributor
Contributor
Jump to solution

This worked, thanks. In my case, it seems that it started after trying to migrate a machine to another host during a partly system inconsistency (a storage connection was gone for a moment, I wanted to "rescue" the VM to another host but this seems to have caused that this error in Veeam)