Unsolved
This post is more than 5 years old
10 Posts
0
1247
March 11th, 2015 11:00
MSSQL database restore does not work if point-in-time falls when a full backup was running
Hi all,
I ran into the following problem and kindly ask your help:
SQL Server 2008 R2 Std
EMC Networker Module for SQL Server Ver. 5.2.2.23
I need to restore a MSSQL database with nsrsqlrc.exe with a point-in-time at 2015-03-10 00:10:00, but it does not work because in that minute a full backup was running on that database (backup started at 2015-03-10 00:03:02 and completed at 2015-03-10 00:18:26).
This is my cmd:
"C:\Program Files\Legato\nsr\bin\nsrsqlrc.exe" -s -c " " -f -d "MSSQL:Copyof " -C "' '=' ','' '=' '" -t "Tue Mar 10 00:10:00 2015" "MSSQL: "
It does not work because Networker always starts restoring the full backup that was running in that minute and not the previous one. So, of course, when it tries to restore the next log backup, it returns:
The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point..
It should simply execute the restore of the previous full backup and all the log backups until the one after the point-in-time.
So, how can I force nsrsqlrc.exe to start from the previous full backup?!?
Pls help.
Thank you,
RochettaPochetta
ble1
4 Operator
•
14.3K Posts
0
March 11th, 2015 12:00
I believe it was build 29 that took care that DB and TLOG at the same do not cause issues. Eventually, you can try to specify PiT from GUI and see if that makes any difference, but I doubt. I'm not sure if b29 alone is enough to sort it out or you need also backup with b29, but best thing is to open support ticket.
rochettapochetta
10 Posts
0
March 12th, 2015 07:00
Hi Hrvoje,
thank you for your answer.
I didn't take a full and a log backup at the same time. I got a normal backup chain: full1 - log1 - log2 - full2 - log3. There are no backups with overlapped time.
I simply want to restore point-in-time in a second that fall between start and stop of full2 backup.
It should restore full1 - log1 - log2 and log3 with stopat that second, but it always tries to restore full2 and log3 with stopat, completing with error.
Now I'm looking for the NMSQL 5.2.2.29
Do you know if that's the last existing version?
Thank you,
RochettaPochetta
ble1
4 Operator
•
14.3K Posts
0
March 12th, 2015 07:00
Actually, SQL module is no longer supported as NMSQL... it was migrated to NMM which supports same VDI approach just as NMSQL did. I believe for 5.2.2 last build was 29.
What you could try is simply select full DB as pit in GUI. I suspect it takes time earlier that you use, but can't be sure now (once you kick it you can see it from log which arguments it did use including -t option).
rochettapochetta
10 Posts
0
March 12th, 2015 10:00
with Gui ...
If I select full2 backup as pit it restores the database at time full2 backup ended, a later time.
If I mark log2 in cbr and try to set pit in the middle of full2, it tells me pit cannot be later the end time of log2.
If I mark full2 in cbr and try to set pit in the middle of full2, it tells me pit can be changed only for a transaction log backup.
If I mark log3 in cbr and try to set pit in the middle of full2, as above, it restores the database at full2 backup end time, a time later than one I need.
Thank you,
RochettaPochetta