Unsolved
This post is more than 5 years old
46 Posts
0
3680
Unable to restore SQL backup
I am trying to restore sql DB backup i am getting this error,
Error:
Recovering files of client 'MSALESDB-RYD.asd.com' from server 'afg-nw-dr.asd.com' to client 'AFG-NET-MSALES3'.
43708:(pid 4492):Start time: Thu Nov 10 11:51:17 2016
43621:(pid 4492):Computer Name: AFG-NET-MSALES3 User Name: omnibkadm
NSR_CLIENT: MSALESDB-RYD.asd.com;
NSR_SERVER: afg-nw-dr.asd.com;
37725:(pid 4492):Recovering database 'mSales' into 'mSales' ...
4690:(pid 4492):RESTORE database [mSales] FROM virtual_device='Legato#42cca529-2741-48e4-8873-daad29853ebb' WITH move 'mSales18Nov_Data' to 'F:\Restore\mSales\mSales_mSales_mSales18Nov_Data_13986_13260.mdf', move 'mSalesLog' to 'F:\Restore\mSales\mSales_mSales_mSales_log_13986_13260.ldf'
37840:(pid 4492):Error opening tape session for MSSQL:/mSales.
70829:(pid 4492):VDI device did not close properly.
ledugarte
96 Posts
0
November 10th, 2016 06:00
Take a look into applogs. Maybe some details are given in these logs.
ble1
14.3K Posts
0
November 11th, 2016 01:00
As this is directed recovery, make sure permissions are in place (including disk space). Next, check logs in applogs on client, but also on backup server for timeframe when session was running to get more details about real nature of the error.
Kaiser_Kamal
46 Posts
0
November 13th, 2016 21:00
Dear Ble
Permission is full disk space also available .
Error from event viewer .
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1688. Thread=3176. Server. Instance=MSSQLSERVER. VD=Global\Legato#76a72cb1-8406-4343-90e5-e70ef1e0269d_SQLVDIMemoryName_0.
Applogs nsrsql attached.
Best Regards
Kaiser Kamal | Data Center Technician
Al Faisaliah Group Holding Company
P.O. Box 16460 Riyadh 11464| Kingdom of Saudi Arabia
•: +966 11 2439822 Ê: +966 11 243 9999 x 9822
•: kkamal@alfaisaliah.com
Website: www.alfaisaliah.com
ledugarte
96 Posts
0
November 14th, 2016 04:00
Try a recover of a filesystem from afg-nw-dr.asd.com to AFG-NET-MSALES3. If it is OK, we can isolate the problem to SQL.
ElanC
53 Posts
0
November 18th, 2016 00:00
This could be due to the hostname mismatch in the SQL Client and NW Server.
Can you add a host entry for "MSALESDB-RYD.asd.com" in both the machines (SQL client and NW Server) and re-try the restore operation.
Thanks,
Kaiser_Kamal
46 Posts
0
November 20th, 2016 01:00
Hello
Host entry are available on both the servers.
Still failing.
Best Regards
Kaiser Kamal | Data Center Technician
Al Faisaliah Group Holding Company
P.O. Box 16460 Riyadh 11464| Kingdom of Saudi Arabia
•: +966 11 2439822 Ê: +966 11 243 9999 x 9822
•: kkamal@alfaisaliah.com
Website: www.alfaisaliah.com
Diego.Palopoli
32 Posts
0
May 1st, 2021 10:00
Hi Kaiser,
I am sorry to bother you with this, but same issue presented here with a restore of historical data; many tries and log reviewing but nothing useful yet to found the root cause of that error (VDI did not close properly).
Did you finally solved this? Do you remember what was the fix or the underlying aspect of the problem?
Many thanks for any help on this regard.
All the best.
DP
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
May 1st, 2021 21:00
@Diego.Palopoli, the error is quite generic.
Are you using the same version of SQL on your destination server? Also, please share the restore logs from your applogs. The reason for failure might not all be the same.