SQL Staging full database recovery failure
NBU 22.214.171.124 on master/media server and client
Windows 2008 R2 on master and client
SQL Full, Differential as well as Transaction Log backups successful (see SQL-test.jpg attachments).
Scripts used in Scripts.txt
We are able to perform a Full Staged Recovery up to the Differential Backup, not the Transaction Logs.
Screenshot (Restore.jpg) shows Full and Diff grouped together at the top.
All Transaction Log backups show up separately at the bottom of the screen not grouped under the Full and the Diff.
Right-Click, Properties of the log backups does not have the Recovery Set tab.
'Stage Full Recovery' option is also greyed out.
All attempts to restore any of the Transaction logs fail with status 2809 and 13:
11/21/2012 11:42:21 AM - Info bpbrm(pid=6616) listening for client connection 11/21/2012 11:42:21 AM - requesting resource @aaaal 11/21/2012 11:42:21 AM - granted resource MediaID=@aaaal;DiskVolume=_PhysicalLSU;DiskPool=Dxi;Path=_PhysicalLSU;StorageServer=-LSU_10.5.1.177;MediaServer=Master 11/21/2012 11:42:22 AM - Info bpbrm(pid=6616) accepted connection from client 11/21/2012 11:42:22 AM - Info tar32(pid=2628) Restore started 11/21/2012 11:42:22 AM - connected 11/21/2012 11:42:22 AM - Info bptm(pid=5644) start 11/21/2012 11:42:22 AM - started process bptm (5644) 11/21/2012 11:42:22 AM - Info bpdm(pid=5644) reading backup image 11/21/2012 11:42:23 AM - Info bptm(pid=5644) using 30 data buffers 11/21/2012 11:42:24 AM - begin reading 11/21/2012 11:42:29 AM - Error bpbrm(pid=6616) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 11/21/2012 11:42:29 AM - Info tar32(pid=2628) done. status: 13: file read failed 11/21/2012 11:42:29 AM - Error bpbrm(pid=6616) client restore EXIT STATUS 13: file read failed 11/21/2012 11:42:29 AM - restored image be-test_1353414007 - (file read failed(13)); restore time 00:00:08 11/21/2012 11:42:29 AM - end Restore; elapsed time: 00:00:09 MS-SQL-Server policy restore error(2809)
I have in all honesty not looked at any of the logs, but I am 100% sure that the issue is with the fact that the Full, Diff and log backups are not seen as a full set.
We have been doing SQL backups for many years at many customer sites, but have never experienced this.
We were initially unable to select the log backups in the Restore GUI: https://www-secure.symantec.com/connect/forums/netbackup-ms-sql-client-1
EEB from Symantec Support fixed the 'App crash' issue.
We probably need to log another Support call, but I will do anything humanly possible to avoid that...
Finally good news! We
Finally good news!
We received version 2 of dbbackup EEB.
This EEB fixed the GUI problem - I could select the last Transaction Log with full recovery option. Last Full, subsequent Diff and all relevant logs were automatically selected. 'Recovery Set' tab also where it should be.
So, restore was submitted. Full, Diff and first log restored successfully.
Failed on 2nd log after reading/writing some data.
Not sure why this happened - no helpful info in Activity Monitor or in dbclient log. Criptic errors in Event Viewer Application log...
My colleague logged in from home tonight and restored the remaining 3 logs one-by-one, selecting 'Recovered' option on the last log.
Database is up and running!
Event Viewer Application log:
Restore is complete on database 'MPR_2012'. The database is now available.
A BIG thanks to colleagues and online friends for your support!