June 22, 2012 at 6:10 pm
I had created a DMP to do full, differential and log backup. Full wouldn’t run till midnight so differential and log started running, although that was not my intention, as log runs every 20 mins and Differential runs every 1 hour.
But it brought 3 databases to Restoring state.
Any idea why only 3 databases would go to suddenly to restoring state? I have cancelled my DMP for now and restored them using this command
RESTORE DATABASE DatabaseName WITH RECOVERY
June 22, 2012 at 7:47 pm
The only tasks in the Maintenance Plan were to perform full, diff and t-log backups? Were there any other tasks? Was there another job that had restored the database. Is logshipping enabled by chance?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 22, 2012 at 9:22 pm
Were you taking log backups with NoRecovery?
June 22, 2012 at 10:44 pm
Yep. I had 'take tail log backup' option checked. Thanks.
June 23, 2012 at 5:47 am
SQL_Surfer (6/22/2012)
Yep. I had 'take tail log backup' option checked. Thanks.
That option means 'backup the log and switch the database into the restoring state'.
It's not an option that should be checked for regular log backups, it's only for when you are backing up the tail of the log in preparation for restoring a backup over that database.
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply