1. Support
  2. Knowledge base
  3. 100010232

VM Restore fails with "file write failed" status 2820 error

Article: 100010232
Last Published: 2013-08-26
Ratings: 0 1
Product(s): NetBackup & Alta Data Protection

Problem

VMware SAN based restore fails with "socket write failed" status 2820 error

- vCenter sees virtual machine created successfully but during write to datastore fails.
- Attempts to restore to alternate datastore results in same issue
- All permissions on vCenter and backup host has been checked.

Error Message

Restore Status
...
...
22/07/2013 11:29:22 AM - begin reading
22/07/2013 11:42:40 AM - Critical bpbrm(pid=7060) from client nbexxxxxxxxxxxxx: FTL - Virtual machine restore: file write failed 
22/07/2013 11:42:40 AM - Critical bpbrm(pid=7060) from client nbexxxxxxxxxxxxx: FTL - Virtual machine restore: file write failed 
22/07/2013 11:42:42 AM - Info tar32(pid=3068) done. status 5         
22/07/2013 11:42:42 AM - Info bptm(pid=1924) EXITING with status 24 <----------       
22/07/2013 11:42:42 AM - Info tar32(pid=3068) done. status: 185         
22/07/2013 11:42:42 AM - Info tar32(pid=3068) done. status: 24: socket write failed      
22/07/2013 11:42:42 AM - Error bpbrm(pid=7060) client restore EXIT STATUS 24: socket write failed    
22/07/2013 11:44:12 AM - restored image WP200A006_1373666722 - (the restore failed to recover the requested files(5)); restore time 00:18:24
22/07/2013 11:44:12 AM - end Restore; elapsed time: 00:18:26
VMware policy restore error(2820)
 
tar
11:42:40.855 AM: [3068.7052] <16> tar_restore_vxms::errorHandler: VXMS MESSAGE - severity 90, message 1: fiml_write_vix_file pathname = <vix>[EMC LUN 06 Prod] WP200A006_Restore/WP200A006_Restore.vmdk, message 2 = vfm_write failed: err = 11
11:42:40.855 AM: [3068.7052] <16> tar_restore_vxms::errorHandler: VXMS MESSAGE - severity 90, message 1: fiml_write_file pathname = <vix>[EMC LUN 06 Prod] WP200A006_Restore/WP200A006_Restore.vmdk, message 2 = fiml_write_vix_file failed stat = 11 
11:42:40.855 AM: [3068.7052] <16> tar_restore_vxms::writeData: fiml_write_file failed error = 11
11:42:40.855 AM: [3068.7052] <2> tar_base::V_vTarMsgW: FTL - Virtual machine restore: file write failed
11:42:40.855 AM: [3068.7052] <2> tar_base::V_vTarMsgW: FTL - Virtual machine restore: file write failed
 
bpbrm
11:42:40.574 [7060.6972] <2> bpbrm write_msg_to_progress_file: (293754.001) TAR - EMC LUN 06 Prod:\WP200A006\WP200A006.vmdk
11:42:40.855 [7060.6972] <32> bpbrm main: from client nbexxxxxxxx: FTL - Virtual machine restore: file write failed
11:42:40.855 [7060.6972] <2> set_job_details: Tfile (293754): LOG 1374457360 32 bpbrm 7060 from client nbexxxxxxxx: FTL - Virtual machine restore: file write failed
11:42:40.855 [7060.6972] <2> send_job_file: job ID 293754, ftype = 3 msg len = 126, msg = LOG 1374457360 32 bpbrm 7060 from client nbexxxxxxxx: FTL - Virtual machine restore: file write failed
 
VxMS
   01:42:40.0855 : g_vixInterfaceLogger:bvix.cpp:1833 <INFO> : diskLibPlugin: 2013-07-22T11:42:40.855+10:00 [07052 error 'BlockList'] Invalid argument: . (Is the disk part of the snapshot you are trying to mount?)
   01:42:40.0855 : g_vixInterfaceLogger:bvix.cpp:1833 <INFO> : diskLibPlugin: 2013-07-22T11:42:40.855+10:00 [07052 error 'Default'] San transport error: The specified request is invalid.
   01:42:40.0855 : g_vixInterfaceLogger:bvix.cpp:1833 <INFO> : DISKLIB-LIB   : RWv failed ioId: #194126 (318) (62) .
   01:42:40.0855 : vdWrite:xInterface.cpp:576 <ERROR> : Returning: 1365799600129

Cause

Virtual machine was originally created with VMware thin provisioning disk option.

As the behavior of thin provisioning disk will dynamically initialize or commit blocks as the data is written to the disk there may have been a problem with dynamic provision in VMware causing allocating block error in vCenter event logs and a series of write errors in the Netbackup logs.

Solution

Change VMware disk format from "Original Provisioning" to "Thick Provisioning with Lazy Zeroed" and triggered same restore using same recovery host/vCenter server.

Ensure there is enough space available in the target datastore to perform thick provisioning disk format.


Applies To

ESX: 4.1
Netbackup 7.5.0.4
Media server: Windows 2003 64bit(64GB RAM)
Restore: vCenter server
Transport Mode: SAN

Attachments

Was this content helpful?

Article Languages