SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database went into Restoring State for unknown reason


Database went into Restoring State for unknown reason

Author
Message
Welsh Corgi
Welsh Corgi
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10118 Visits: 4894
I have a Database that went into Restoring State for unknown reason.

I had recovered it this morning. Then I performed a Full and Transaction Log Backup.

I treid restoring to a new database but I get errors that the device does not exist.

I specified a Database with a Restore Sufix for now for proof of concept.

Could I do the following?

1.Stop the service (MSSQLSERVER);
2.Rename or delete the Database and Log files (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data...) or wherever you have the files;
3.Start the service (MSSQLSERVER);
4.Delete the database with problem;
5.Restore the database again.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Matt Crowley
Matt Crowley
SSC-Addicted
SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)SSC-Addicted (435 reputation)

Group: General Forum Members
Points: 435 Visits: 469
I would run a DBCC CHECKDB against the restored copy (probably off hours, as this will hit the disk pretty hard), just to be sure everything is correct with the restored copy. I would be much more concerned over the root cause of the database going to a restoring state. Without knowing that, this particular database could surprise you at just about any time.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86655 Visits: 45254
Restoring or recovering?

A DB will go restoring if someone runs BACKUP LOG ... WITH NORECOVERY or runs a restore over the database and specifies NORECOVERY. In either case running RESTORE DATABASE <db name> WITH RECOVERY will bring it back online. Can also happen if someone starts a restore and stops the restore part way through (perhaps realising they were restoring over the wrong DB)

A database will go into the recovering state if SQL is restarted and that DB was not cleanly shut down. It's a temporary state, once recovery has completed the DB will come online.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Welsh Corgi
Welsh Corgi
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10118 Visits: 4894
GilaMonster (11/6/2013)
Restoring or recovering?

A DB will go restoring if someone runs BACKUP LOG ... WITH NORECOVERY or runs a restore over the database and specifies NORECOVERY. In either case running RESTORE DATABASE <db name> WITH RECOVERY will bring it back online. Can also happen if someone starts a restore and stops the restore part way through (perhaps realising they were restoring over the wrong DB)

A database will go into the recovering state if SQL is restarted and that DB was not cleanly shut down. It's a temporary state, once recovery has completed the DB will come online.


I went into a restoring state.

I was able to restore the database.

Thank you.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86655 Visits: 45254
Then check jobs, maintenance plans, make sure you don't have something trying to do a tail-log backup (backup with norecovery) and that no one restored the wrong DB (error log and backup/restore history will help there)

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Grant Fritchey
Grant Fritchey
SSC-Dedicated
SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)

Group: General Forum Members
Points: 39396 Visits: 32630
GilaMonster (11/6/2013)
Restoring or recovering?

A DB will go restoring if someone runs BACKUP LOG ... WITH NORECOVERY ....


In what might be an epic role reversal, don't you mean RESTORE LOG etc.?

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86655 Visits: 45254
Grant Fritchey (11/7/2013)
GilaMonster (11/6/2013)
Restoring or recovering?

A DB will go restoring if someone runs BACKUP LOG ... WITH NORECOVERY ....


In what might be an epic role reversal, don't you mean RESTORE LOG etc.?


No, I really do mean backup.

If you try a RESTORE LOG on a database that's online, all you'll get is an error (no files are ready to roll forward), the database state won't change. If you do a tail log backup (BACKUP LOG ... WITH NORECOVERY) then you're telling SQL you want to take a log backup and ensure that no more transactions can be done after the backup (it's done prior to starting a restore or moving a database). It will then do the backup (to DISK or whereever else) and once the backup completes the database will switch into the restoring state. This ensures that the log backup captured the very last transactions that ran so that none are lost.

The problem is, both the backup wizard and the maintenance plan backup task have the option 'back up the tail of the log' in them, if that's selected erroneously (especially in a maintenance plan), then the database will appear to switch into RESTORING for no good reason.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Steve Jones
Steve Jones
SSC Guru
SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)

Group: Administrators
Points: 61933 Visits: 19099
GilaMonster (11/7/2013)

No, I really do mean backup.

If you try a RESTORE LOG on a database that's online, all you'll get is an error (no files are ready to roll forward), the database state won't change. If you do a tail log backup (BACKUP LOG ... WITH NORECOVERY) then you're telling SQL you want to take a log backup and ensure that no more transactions can be done after the backup (it's done prior to starting a restore or moving a database). It will then do the backup (to DISK or whereever else) and once the backup completes the database will switch into the restoring state. This ensures that the log backup captured the very last transactions that ran so that none are lost.

The problem is, both the backup wizard and the maintenance plan backup task have the option 'back up the tail of the log' in them, if that's selected erroneously (especially in a maintenance plan), then the database will appear to switch into RESTORING for no good reason.



Wow, did not know this. I was about to ask what Grant did.

And yet, it does cause it to go into restoring:
CREATE DATABASE MyRestoreTest
;
GO
BACKUP DATABASE MyRestoreTest TO DISK ='myrestoretest.bak';
GO
CREATE TABLE mytable( id INT)
;
GO
BACKUP LOG myrestoretest TO DISK = 'myrestoretest_log.trn' WITH norecovery



and I can get things back.

RESTORE DATABASE myrestoretest WITH recovery


Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Jeffrey Williams 3188
Jeffrey Williams 3188
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7645 Visits: 9966
I believe you can also use BACKUP DATABASE ... WITH NORECOVERY; and it does the same thing. Very good for taking a last backup when migrating to a new system.

Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

Sreekanth B
Sreekanth B
SSChasing Mays
SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)SSChasing Mays (605 reputation)

Group: General Forum Members
Points: 605 Visits: 2060
But for "BACKUP LOG DB_Name...........WITH NORECOVERY" to run successfully, SQL server needs exclusive access on the respective database right? If there's any active session in the Database, it won't let you take log backup with norecovery and fails with below error and shouldn't go to "RESTORING" state. Please correct me If I am wrong...

Msg 3101, Level 16, State 1, Line 1
Exclusive access could not be obtained because the database is in use.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search