Video Screencast Help
Search Video Help Close Back
to help

Netbackup 7.5 for hyper-v restore error status: 24: socket write failed

Created: 22 Nov 2012 | 2 comments
phaul's picture
0 0 Votes
Login to vote

Hi Guys,

We're trying to restore a 1 hyper-v virtual machine in a CSV environment using Netbackup 7.5 for linux. But we 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 2 CommentsJump to latest comment

Joseph_TKLee's picture

I have done several restore testings.

Possible actions below would be recommended.

- Change the client name to IP address on master server

- Check /etc/hosts on the client if media server IP is registered.

- Add media server into the client's server access list property on master server

 

Hope this would give you an idea to fix.

cheers,

0
Login to vote
  • Actions
phaul's picture

Hi Joseph,

 

Thanks for your response. I already did these steps but the restore still fails.

 

Thanks.

0
Login to vote
  • Actions