ISSUE:
Hyper-V restores failing with "EXIT STATUS 24:  socket write failed"

SOLUTION:
In the NetBackup for Hyper-V Guide, version 6.5.4 states the following:

"When you restore the virtual machine to a Hyper-V server that has a virtual machine of the same GUID, you must select the Overwrite virtual machine option.  Otherwise, the restore fails."

You must select the "Overwrite virtual machine" option when configuring a full Hyper-V virtual machine restore, or manually delete the existing Hyper-V virtual machine before running the restore.

TROUBLESHOOTING STEPS:
The Detailed Status tab for the restore in the Activity Monitor shows the following error:

10/26/2009 9:31:06 AM - Critical bpbrm(pid=2836) from client <hyper-v host>: FTL - Initial Hyper-V snapshot processing failed  
10/26/2009 9:31:06 AM - Critical bpbrm(pid=2836) from client <hyper-v host>: FTL - Final Hyper-V snapshot processing failed  
10/26/2009 9:31:06 AM - Error bptm(pid=4788) cannot write data to socket, 10054      
10/26/2009 9:31:07 AM - restored image <virtual_machine>_1256560997 - (the restore failed to recover the requested files(5)); restore time 00:00:16
10/26/2009 9:31:07 AM - end Restore; elapsed time: 00:00:20
the restore failed to recover the requested files(5)
10/26/2009 9:31:11 AM - Error bpbrm(pid=2836) client restore EXIT STATUS 24: socket write failed

TAR on the Hyper-V host will also have the following message:

9:31:06.478 AM: [2664.2196] <16> tar_restore_vxms::errorVxFIHandler: VXFI MESSAGE - severity 3, vss:Mon Oct 26 2009 09:31:06.478000 <Thread id - 2196> VssNode::doRestore VM with same GUID exists & VFI_RESTORE_OVERWRITE is not set, existing with error

REFERENCE:
NetBackup for Hyper-V Guide, version 6.5.4
http://support.veritas.com/docs/318358

STATUS CODE:
Status 24, Status 5