cancel
Showing results for 
Search instead for 
Did you mean: 

MS-SQL database restore failed

southlend
Level 2

I am a beginner of netbackup.

My master server is redhat in vmware ESXI and sql server is windows2012 in vmware ESXI

I restore MS-SQL database using move option but it failed as following

I don't know why and what to do.

Could someone help me plz

 

2019. 6. 12 오후 9:11:17 - begin Restore
2019. 6. 12 오후 9:11:17 - restoring from image nbuclient_1560336528
2019. 6. 12 오후 9:11:18 - Info bprd (pid=15620) Found (5) files in (1) images for Restore Job ID 177.xxx
2019. 6. 12 오후 9:11:18 - Info bprd (pid=15620) Restoring from copy 1 of image created Wed Jun 12 19:48:48 2019 from policy nbuclient_DB
2019. 6. 12 오후 9:11:18 - Info bpbrm (pid=15630) nbuclient is the host to restore to
2019. 6. 12 오후 9:11:18 - Info bpbrm (pid=15630) reading file list for client
2019. 6. 12 오후 9:11:18 - Info bpbrm (pid=15630) listening for client connection
2019. 6. 12 오후 9:11:19 - Info bpbrm (pid=15630) accepted connection from client
2019. 6. 12 오후 9:11:19 - Info dbclient (pid=2776) Restore started
2019. 6. 12 오후 9:11:19 - Info bpbrm (pid=15630) bptm pid: 15631
2019. 6. 12 오후 9:11:19 - Info bptm (pid=15631) start
2019. 6. 12 오후 9:11:19 - started process bptm (pid=15631)
2019. 6. 12 오후 9:11:19 - Info bptm (pid=15631) reading backup image
2019. 6. 12 오후 9:11:19 - Info bptm (pid=15631) using 30 data buffers
2019. 6. 12 오후 9:11:19 - Info bptm (pid=15631) spawning a child process
2019. 6. 12 오후 9:11:19 - Info bptm (pid=15631) child pid: 15633
2019. 6. 12 오후 9:11:20 - begin reading
2019. 6. 12 오후 9:11:20 - Info bptm (pid=15631) waited for empty buffer 0 times, delayed 0 times
2019. 6. 12 오후 9:11:20 - end reading; read time: 0:00:00
2019. 6. 12 오후 9:11:50 - Info dbclient (pid=2776) done. status: 5
2019. 6. 12 오후 9:11:50 - Error bptm (pid=15633) cannot write data to socket, 연결이 상대편에 의해 끊어짐
2019. 6. 12 오후 9:11:50 - Error bptm (pid=15633) The following files/folders were not restored:
2019. 6. 12 오후 9:11:50 - Error bptm (pid=15633) UTF - /SQLSERVER.MSSQL7.SQLSERVER.db.test.~.7.001of001.20190611184730..C
2019. 6. 12 오후 9:11:50 - Info bptm (pid=15631) EXITING with status 24 <----------
2019. 6. 12 오후 9:11:50 - Info dbclient (pid=2776) done. status: 24: socket write failed
2019. 6. 12 오후 9:11:50 - Error bpbrm (pid=15630) client restore EXIT STATUS 24: socket write failed
2019. 6. 12 오후 9:11:51 - restored from image nbuclient_1560336528; restore time: 0:00:34
2019. 6. 12 오후 9:11:51 - end Restore; elapsed time 0:00:34
MS-SQL-Server policy restore error  (2809)
1 ACCEPTED SOLUTION

Accepted Solutions

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

it is usually some mistyping in move template script.

Single file restore is working?

In place database restore (without move script) is working?

Inspect error appearing in MS SQL Agent interface on db server, Activity Monitor Job detaiils are not very useful for this troubleshooting.

Regards

Michal

 

View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

it is usually some mistyping in move template script.

Single file restore is working?

In place database restore (without move script) is working?

Inspect error appearing in MS SQL Agent interface on db server, Activity Monitor Job detaiils are not very useful for this troubleshooting.

Regards

Michal

 

Thanks a lot

It is helpful to me