Video Screencast Help

Netbackup for Hyper-v Unable to restore virtual machine status: 24: socket write failed

Created: 16 Nov 2012 • Updated: 16 Nov 2012 | 3 comments
phaul's picture

Hi Guys,

 

We have Hyper-v in a CSV environment in Windows Server 2008 R2. I tried performing restore to other hyper-v host but i always got this error:

11/16/2012 18:02:34 - begin Restore
11/16/2012 18:02:39 - media needed: STK555
11/16/2012 18:02:39 - restoring from image vsmcadlic01_1352172322
11/16/2012 18:02:39 - Info bprd (pid=1218) Restoring from copy 1 of image created Tue Nov  6 11:25:22 2012
11/16/2012 18:02:47 - requesting resource STK555
11/16/2012 18:02:47 - granted resource  STK555
11/16/2012 18:02:47 - granted resource  Drive371
11/16/2012 18:04:35 - requesting resource STK555
11/16/2012 18:04:35 - granted resource  STK555
11/16/2012 18:04:35 - granted resource  Drive371
11/16/2012 18:05:32 - restored from image vsmcadlic01_1352172322; restore time: 0:02:53
11/16/2012 18:05:37 - end Restore; elapsed time 0:03:03
11/16/2012 18:10:07 - Info bptm (pid=15788) start
11/16/2012 18:10:07 - started process bptm (pid=15788)
11/16/2012 18:10:07 - Info bpdm (pid=15788) reading backup image
11/16/2012 18:10:07 - Info bptm (pid=15788) using 30 data buffers
11/16/2012 18:10:07 - Info bptm (pid=15788) spawning a child process
11/16/2012 18:10:07 - Info bptm (pid=15788) child pid: 12444
11/16/2012 18:10:07 - Info bptm (pid=12444) start
11/16/2012 18:10:07 - started process bptm (pid=12444)
11/16/2012 18:10:11 - Info bptm (pid=15788) Waiting for mount of media id STK555 (copy 1) on server svrmdbcsmhost01.
11/16/2012 18:10:11 - started process bptm (pid=15788)
11/16/2012 18:10:11 - mounting STK555
11/16/2012 18:10:14 - Info bptm (pid=15788) INF - Waiting for mount of media id STK555 on server svrmdbcsmhost01 for reading.
11/16/2012 18:10:24 - mounted STK555; mount time: 0:00:13
11/16/2012 18:10:24 - Info bptm (pid=15788) STK555
11/16/2012 18:10:28 - Info bptm (pid=15788) INF - Waiting for positioning of media id STK555 on server svrmdbcsmhost01 for reading.
11/16/2012 18:10:28 - positioning STK555 to file 13
11/16/2012 18:10:28 - positioned STK555; position time: 0:00:00
11/16/2012 18:10:31 - begin reading
11/16/2012 18:10:31 - Info bptm (pid=15788) waited for empty buffer 1 times, delayed 10 times
11/16/2012 18:10:31 - end reading; read time: 0:00:00
11/16/2012 18:10:32 - Info bptm (pid=15788) completed reading backup image
11/16/2012 18:10:32 - Info bptm (pid=15788) EXITING with status 0 <----------
11/16/2012 18:10:34 - Info bpbrm (pid=17228) svrmdbcsmhost05 is the host to restore to
11/16/2012 18:10:34 - Info bpbrm (pid=17228) reading file list from client
11/16/2012 18:10:40 - connecting
11/16/2012 18:10:40 - Info bpbrm (pid=17228) starting bptm
11/16/2012 18:11:54 - Info tar32 (pid=14008) Restore started
11/16/2012 18:11:54 - connected; connect time: 0:00:00
11/16/2012 18:11:55 - Info bptm (pid=10024) start
11/16/2012 18:11:55 - started process bptm (pid=10024)
11/16/2012 18:11:55 - Info bpdm (pid=10024) reading backup image
11/16/2012 18:11:55 - Info bptm (pid=10024) using 30 data buffers
11/16/2012 18:11:55 - Info bptm (pid=10024) spawning a child process
11/16/2012 18:11:55 - Info bptm (pid=10024) child pid: 18368
11/16/2012 18:11:55 - Info bptm (pid=18368) start
11/16/2012 18:11:55 - started process bptm (pid=18368)
11/16/2012 18:11:59 - mounted STK555
11/16/2012 18:11:59 - Info bptm (pid=10024) STK555
11/16/2012 18:12:02 - Info bptm (pid=10024) INF - Waiting for positioning of media id STK555 on server svrmdbcsmhost01 for reading.
11/16/2012 18:12:02 - positioning STK555 to file 13
11/16/2012 18:12:02 - positioned STK555; position time: 0:00:00
11/16/2012 18:12:06 - begin reading
11/16/2012 18:12:50 - Critical bpbrm (pid=17228) from client svrmdbcsmhost05: FTL - Initial Hyper-V snapshot processing failed
11/16/2012 18:12:50 - Error bptm (pid=18368) cannot write data to socket, 10054
11/16/2012 18:12:51 - Info bptm (pid=10024) EXITING with status 24 <----------
11/16/2012 18:12:53 - Info tar32 (pid=14008) done. status: 24: socket write failed
11/16/2012 18:12:53 - Error bpbrm (pid=17228) client restore EXIT STATUS 24: socket write failed
Failed to get status code information (2821)

 

Comments 3 CommentsJump to latest comment

CraigV's picture

...moved to the correct forum (I think...it looks like this is a NBU query!).

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

captain jack sparrow's picture

please share bpfis  logs

also show VSS writer status  .. DO you see any events logged under app 

There are few VSS issues which are out of NBU scope and requires MS to intervene

 

 Cheers !!!

CJS

 

barrowboy's picture

Had a similar problem with a Hyper-V restore to its original location. Restore failed with :-

3-May-2013 09:12:11 - Critical bpbrm (pid=2200) from client rhbarhypv05: FTL - Initial Hyper-V snapshot processing failed
13-May-2013 09:12:11 - Error bptm (pid=5032) cannot write data to socket, 10054
13-May-2013 09:12:12 - restored from image HRHBARTCD06.purple.zebra.ad_1368100136; restore time: 0:02:00
13-May-2013 09:12:13 - end Restore; elapsed time 0:02:02
13-May-2013 09:12:18 - Error bpbrm (pid=2200) client restore EXIT STATUS 24: socket write failed
the restore failed to recover the requested files  (5)

The problem was the Hyper-V guest was in 'saved critical ' state on the host. We had to either completly delete the guest or get it into offline mode. Once we did this the restore worked ok