Networker

[Networker] MSSQL recover with "norecover" option - not returning the right database ...

2012-06-22 07:50:53
Subject: [Networker] MSSQL recover with "norecover" option - not returning the right database ...
From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 22 Jun 2012 07:41:31 -0400
Here's a weird one. My DBAs need a MS SQL DB restored, and they need it 
done as a "No Recover" sort of restore. That's (apparently) a special kind 
of MS SQL restore, which would allow them to replay the transaction logs, 
and bring the DB back to the point in time they want.

So I go to the client (a SQL 2008 cluster, so it's a virtual client), fire 
up the SQL Module GUI, choose a recover (copy), and browse back to the 
date I want (2012-06-19), choose my DB, see that it has the right size for 
that date (567G - it's a big one), and change the properties to choose a 
"No Recover"  restore, and change the destination path so it goes to a new 
folder. All well and good, and just like the manual says.

But what I get back is the database as of 2012-06-20 (i.e, the next day). 
When my guys open the restored DB, they say it reports that it was backed 
up 2012-06-19, and at the time of the backup of 2012-06-20.

I did both an mminfo and and nsrinfo, and I see my file as of 2012-06-19. 

So how come I get the right file as a "normal" recovery, and do *not* get 
the right file when I choose the same file (same browse time, choosing the 
same file), but change the recover option from "normal" to "no recover"?

I had 2 different Tech Support folks trying to help me last night. Since 
we're desperate for *something*, I did a "normal" recovery overnight, so 
my guys at least have something (you can't replay transaction logs against 
a "normal" recovery, they tell me. But at least they have all the records, 
before they wrongly deleted them on 2012-06-20). I did indeed get 567G. 
And when the DBAs open this file, it does indeed say backed up 2012-06-19 
22:15PM.

Note that these are FULL backups, not incremental.

D:\Program Files\Legato\Scripts>mminfo -avot -q "ssid=3856740907" -r 
volume,client,name,level,totalsize(2),nsavetime,savetime(22),sscomp(22),ssflags
 volume        client     name                             lvl total save 
time        date              ss completed     ssflags
008068         SQL-Client     MSSQL:        full 567 GB 1340158503 
6/19/2012 10:15:03 PM 6/19/2012 11:25:08 PM vF
AFTD.155 SQL-Client MSSQL:             full 567 GB 1340158503 6/19/2012 
10:15:03 PM 6/19/2012 11:25:08 PM vF
AFTD.155.RO SQL-Client MSSQL:     full 567 GB 1340158503 6/19/2012 
10:15:03 PM 6/19/2012 11:25:08 PM vF

So you see I have the backup. But the "no recover" doesn't give me this, 
but the "normal" recovery does. The "no recover" gives me this:

 volume        client     name                             lvl total save 
time        date              ss completed     ssflags
008048         SQL-Client     MSSQL:       full 174 GB 1340244846 
6/20/2012 10:14:06 PM 6/20/2012 10:39:10 PM vF
AFTD.155 SQL-Client MSSQL:             full 174 GB 1340244846 6/20/2012 
10:14:06 PM 6/20/2012 10:39:10 PM vF
AFTD.155.RO SQL-Client MSSQL:     full 174 GB 1340244846 6/20/2012 
10:14:06 PM 6/20/2012 10:39:10 PM vF

That's what the NW log shows as being restored - 174G. And that's the date 
and time the recovered DB shows - 2012-06-20 10:14PM. Even tho I asked for 
the file for the 19th ...

And I'm still waiting for Tech Support to call me back this morning; 
apparently they have a large number of Sev 1 calls. Meanwhile, we're 
sitting here not really able to do what we need to do with this DB.

Anybody have any ideas?
-- 
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>

<Prev in Thread] Current Thread [Next in Thread>