September 17, 2012 at 2:42 am
Can anyone else confirm that there is a bug in the gui that won't allow you to do diff or log restores. Works fine with T-SQL, but not with the gui.
I tested by running a full backup, then a log backup, then a diff, with making small changes to a table in between. Couldn't restore either the log or the diff via the gui, but fine if i create a script from the gui window and run that.
Am i missing something or is this a bug? My tests couldn't have been simpler.
Darren
September 17, 2012 at 4:29 am
Why on earth would you want to use the GUI anyway?
But, no, I just did a test. Ran a full backup, modified data, ran a differential backup. Made sure all my connections were clear of that database, Ran a restore of the full and differential. All from the gui.
Sorry, it worked fine.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 17, 2012 at 4:59 am
How patronising!
I can reproduce this on a vanilla 2008 R2 server, with a vanilla SQL install.
Maybe you are just too good and i'm just a dummy, but what am i supposed to do now?
Thanks for no help.
It always makes me wonder why people would bother replying just to tell someone that they are stupid.
I am obviously doing something wrong. I understand that. But it would be really nice to improve my skills a little and know why it doesn't work.
Someone could do with getting out a little more and understanding that people aren't all perfect. I never actually read the sticky that says that only experts were allowed on here.
September 17, 2012 at 5:15 am
dt2 (9/17/2012)
but what am i supposed to do now?
You can start by adjusting your attitude. We're volunteers, we post in our spare time and insulting someone who's trying to help is not a good way to get further help.
Now, to your question, no, there is no such bug. Diff and log restores work fine in 2008, 2008 R2. I don't have a 2012 instance on hand, but were there such a bug it would have been picked up some time back.
Can you go step-by-step (with screenshots if necessary) through what you're doing, with exact error messages and maybe someone here can see what the problem is.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 17, 2012 at 6:21 am
dt2 (9/17/2012)
How patronising!I can reproduce this on a vanilla 2008 R2 server, with a vanilla SQL install.
Maybe you are just too good and i'm just a dummy, but what am i supposed to do now?
Thanks for no help.
It always makes me wonder why people would bother replying just to tell someone that they are stupid.
I am obviously doing something wrong. I understand that. But it would be really nice to improve my skills a little and know why it doesn't work.
Someone could do with getting out a little more and understanding that people aren't all perfect. I never actually read the sticky that says that only experts were allowed on here.
I'm sorry if my post came across as patronizing. I was honestly trying to help. Your first post said:
Can anyone else confirm that there is a bug in the gui that won't allow you to do diff or log restores. Works fine with T-SQL, but not with the gui.
I tested by running a full backup, then a log backup, then a diff, with making small changes to a table in between. Couldn't restore either the log or the diff via the gui, but fine if i create a script from the gui window and run that.
Am i missing something or is this a bug? My tests couldn't have been simpler.
I did exactly what you wanted, I confirmed that there is no bug. The GUI works. So the issue must be elsewhere. I thought that was what you needed. If you needed more, just say that. I'm not a mind reader.
When you say it doesn't work, are you getting an error? What error? If not an error, you mean the differential restore runs, but you're not seeing the changed data? Are the backups going to separate files or are you stacking them within a single backup set. That would change how to do the restore.
Also, you posted to a 2012 forum, and that's what I tested on. If you're running 2008 R2, you might want to post to the 2008 forum because the answers might not be the same in all situations.
Again, apologies if the tone came off wrong. It wasn't intended.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 17, 2012 at 6:53 am
I may of got a bit carried away too...sorry.
Yes it was in 2012. Simply a vanilla build 2008 R2 server, with vanilla sql 2012 instance.
I created a new database, with a new table and made sure that the recovery mode was set to full.
Took a full backup, then amended the table data, then took a diff.
They were in separate files.
I restored the full backup with NORECOVERY, then tried to restore the diff but the OK button was greyed out with a message at the top of the restore window regarding LSNs being incorrect.
I checked the LSNs were ok from the msdb.backupset table, which they were.
Then i created a script from the gui, which i executed, and it worked correctly as expected.
If you can't reproduce the problem i will recreate the problem on my test box and post screen shots of the gui window with the error and the query from the backupset table showing the LSNs.
Probably won't be until tomorrow though as we are having problems with phones at the moment and i have an engineer in!
Any help is much appreciated.
Darren
September 17, 2012 at 7:21 am
dt2 (9/17/2012)
I may of got a bit carried away too...sorry.Yes it was in 2012. Simply a vanilla build 2008 R2 server, with vanilla sql 2012 instance.
I created a new database, with a new table and made sure that the recovery mode was set to full.
Took a full backup, then amended the table data, then took a diff.
They were in separate files.
I restored the full backup with NORECOVERY, then tried to restore the diff but the OK button was greyed out with a message at the top of the restore window regarding LSNs being incorrect.
I checked the LSNs were ok from the msdb.backupset table, which they were.
Then i created a script from the gui, which i executed, and it worked correctly as expected.
If you can't reproduce the problem i will recreate the problem on my test box and post screen shots of the gui window with the error and the query from the backupset table showing the LSNs.
Probably won't be until tomorrow though as we are having problems with phones at the moment and i have an engineer in!
Any help is much appreciated.
Darren
OK, I think I've got the issue. The GUI is trying to "help" you, so it wants to see the full and the differential that you'll be restoring. If you add both devices, the process should work fine. If you only add the differential, the GUI, in it's attempt to help, won't be able to restore the differential. It's not a bug. It's how the silly thing works. Again, all part of "helping" you.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 17, 2012 at 7:57 am
Yes, thats exactly it!
Thank you very much for that, you've hit the nail on the head!
I knew i wasn't going crazy. :crazy:
This does however smell to me like a bug!
The gui is telling me that there is a break in the LSN chain when there is not. If it allows me to restore both at once, then why is it an error when restoring them separately?
Again, many thanks for taking the time to check.
Darren
September 17, 2012 at 8:09 am
Because the GUI is trying to assist you through the process. And if you haven't got the full backup, the restore is going to go south. It's only validating against the files it has. It's not checking the database or it's state. It makes sense (in a twisted sort of way) as long as you know that the GUI is desperately trying to make things easy for you.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply