Veeam Backup Error, Possibly Mapped Raw LUN Related

[AlaskanBrewing]

I just added a new Win2008 SP2 x64 server that we'll be replacing our old file server with. In order to do some testing for migrating over the original drives, I cloned our IT drive and attached it as a Mapped Raq LUN to the new file server. This worked well with all the files and permissions intact. However the Veeam Backup logs this morning errored out on the VM backup.

Code: Select all

Backing file "nfc://conn:esx1,nfchost:ha-host,stg:49baec10-e5af4218-036c-001b212c9649@HAL/HAL_1-rdmp.vmdk" Backup failed Client error: File does not exist or locked. VMFS path: [[ESX1] HAL/HAL_1-rdmp.vmdk]. Please, try to download specified file using connection to the ESX server where the VM registered.

Failed to create NFC download stream. NFC path: [nfc://conn:esx1,nfchost:ha-host,stg:49baec10-e5af4218-036c-001b212c9649@HAL/HAL_1-rdmp.vmdk]. Cannot backup file in the service console mode. File: [nfc://conn:esx1,nfchost:ha-host,stg:49baec10-e5af4218-036c-001b212c9649@HAL/HAL_1-rdmp.vmdk]. VBK: [veeamfs:4:b09feb04-9cc4-4262-9af3-19ad6e292297 (528)/HAL_1-rdmp.vmdk@G:\VMs\ESX1\ESX1 Host Backup.vbk]. RBK: [veeamfs:4:b09feb04-9cc4-4262-9af3-19ad6e292297 (528)/HAL_1-rdmp.vmdk@]. Server error: End of file

Veeam 3.1 on ESXi 3.5 158874 (won't be upgrading any further due to the licensing changes)

VM size is 30GB
Raw Lun is 20GB

To try and stop the backup from repeating and erroring out I changed Veeam Backup Job to only backup Selected Disks SCSI (0:0) -> (0:9), and placed the Raw LUN on (0:10) so it'd be ignored.

Any ideas on what the error is for or how to fix it? I see there is a HAL_1-rdmp.vmdk (20.1 GB) file, along with a HAL-flat.vmdk (30GB) file.

This is also the first time we've mapped a raw LUN to ESXi like this and w/t Veeam Backup, hence why I thought they were related along with Veeam seeing the VM as having 50GB total size, and 30GB processed size.

[AlaskanBrewing]

Win2k8 VSS related? rest of the error being reported by veeam still.

"Releasing VM files VSSFreezer: -2147467259 Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x8004231f]."

[Vitaliy S.]

Hello Sir,

Concerning your VSS error please check the Volume Shadow Copy Service (VSS) writer status by running the command
VSSADMIN LIST WRITERS

After please review the output and ensure that the writers are all showing a State of "[1] Stable" and that Last Error is showing "No error." Also you could check the Event Logs at Windows machine for details, there should be VSS errors presented.

Thank you.

[Panajack]

We've had the same error on numerous occassions - in our case the solution was pretty stupidly simple - We have our volumes trimmed down so there is VERY little free space for any growth. On the Windows side during the VSS creation the error is thrown indicating such. Adding addtional space to the active partition allowed for the snapshot to continue without error.

[Vitaliy S.]

Erik, thanks for sharing your experience, much appreciated.

[straycur]

I also had a VM failing with VSS error 0x8004231f . I found posts on the web saying this error mapped to VSS_E_INSUFFICIENT_STORAGE
for example at IBM: http://www-01.ibm.com/support/docview.w ... wg21295293

In fact we had very little space on the C: drive, 333 MB out of 40 GB. Following Panajack's hint, we deleted some obsolete files, and freed up enough space for the Veeam backup to complete successfully. In this case the error was telling us exactly what was wrong, and Panajack's post was good confirmation.

Thanks for pointing to the correct solution !

[veremin]

Thanks, Susan, for confirming reliability of the hint proposed by Panajack; highly-appreciated. Thanks.