This post is more than 5 years old
4 Posts
0
14263
December 9th, 2014 06:00
Problem with restore SQL Server database
Hi
We have a SQL Server cluster with 2 nodes (Windows Server 2008 R2 Enterprise Edition SP1) and one instance (SQL Server 2008 SP4). We have installed NMM 3.01. We were able to set up backup but we can't restore any database. Here is part of output from NetWorker User for SQL Server
37721:(pid 1340):Recovering database 'NetworkerTest' ...
4690:(pid 1340):RESTORE database [NetworkerTest] FROM virtual_device='Legato#7f3b52ee-618d-4e6a-aac1-b47a64e5b799' WITH replace
37840:(pid 1340):Error opening tape session for MSSQL:/NetworkerTest.
70829:(pid 1340):VDI device did not close properly.
After getting the last line operation is not aborted but there is no further action. I can cancel restoring by closing the Restore window.
Thanks in advance for any reply.



pm_1
4 Posts
1
December 10th, 2014 07:00
Hi Carlos
The problem seems to be solved. I have uninstalled NetWorker Module for Microsoft and then NetWorker client. After restarting server I have deleted C:\Program files\EMC Networker directory and installed NetWorker client 8.1.1 and NetWorker Module for Microsoft 3.01 (both installations runnig as administrator). Same time NetWorker Server has been upgraded from 8.1 to 8.2. I don't know what helped but now I can successfuly backup and restore databases.
Thanks for your help.
Best regards
Przemek
CarlosRojas
1.7K Posts
1
December 9th, 2014 06:00
Hello,
Can you please make sure there is no nsrsqlxxxxx.exe processes running in any physical node of the SQL cluster nodes?
Then, can you please set debug level 3 and try a new restore and please add the output here?
Thank you,
Carlos
pm_1
4 Posts
0
December 9th, 2014 08:00
Hello
I can see only nsrexecd.exe, nsrpm.exe and nsrprd.exe on both nodes.
Output from restore with debug level 3 in attachment.
There are two more processes until I cancel the operation - nsrsqlrc.exe and nwmssql.exe.
Thanks
Przemek
1 Attachment
nsr_output_debug_3.txt
pm_1
4 Posts
0
December 10th, 2014 02:00
Hello Carlos
XBSA log is attached. There are two kind of entries:
1) _nwbsa_open_restore_session: System detected error due to: Failed to establish restore session. Exiting. Operation aborted - logged every time I try to restore
2) _nwbsa_is_retryable_error: received a retryable network error (Severity 0 Number -13): busy - logged when scheduled backup is being performed - very often backup of the first database from SQL Server fails but it is the other case
Every time I cancel restoring three events come to Windows Application eventlog:
1) Event ID 1 - SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0). Process=892. Thread=3780. Server. Instance=SQL03. VD=Global\Legato#a5e9c6c5-78a2-478d-a7e6-13b0e62a11e6_SQLVDIMemoryName_0.
2) Event ID 1 - SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=892. Thread=4892. Server. Instance=SQL03. VD=Global\Legato#a5e9c6c5-78a2-478d-a7e6-13b0e62a11e6_SQLVDIMemoryName_0.
3) Event ID 18210 - BackupIoRequest::ReportIoError: read failure on backup device 'Legato#a5e9c6c5-78a2-478d-a7e6-13b0e62a11e6'. Operating system error 995(failed to retrieve text for this error. Reason: 15105).
No events in Windows System eventlog.
Best regards
Przemek
1 Attachment
xbsa.messages
CarlosRojas
1.7K Posts
1
December 10th, 2014 02:00
Thank you Przemek,
Could you please attach the XBSA messages and check if there is any error in the application and system event logs?
Thank you,
Carlos
CarlosRojas
1.7K Posts
1
December 10th, 2014 04:00
Hi Przemek,
I would check first if there is any authentication issue in the daemon.raw from the client, server and storage node if any is used.
Have you tried any other recovery type instead of replace?
Thank you,
Carlos
JEFFREYCUST
3 Posts
0
October 19th, 2020 23:00
Not in our case. We waited 5hours. Went ok without doing anything.