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


Mirror database stuck-in-restoring-state


Mirror database stuck-in-restoring-state

Author
Message
lescobar
lescobar
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 53
Hello everyone

I have two sql servers
It is setup as a mirror databases

1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)

I do not know how this happen
We are able to connect to the database 1 and work in it without any problems

I do get an error message:

Error: [The database "ContinuumDB" cannot be opened. It is acting as a mirror database. BACKUP LOG is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.]
Source: shd-continuum-sql2, Process: SQLiDA
shd-continuum-sql2 Win FS /
N/A defaultBackupSet/

How do I get the database 2 back to show secondary and get rid of restoring ?
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)

Group: General Forum Members
Points: 56405 Visits: 17729
lescobar (7/30/2014)
Hello everyone

I have two sql servers
It is setup as a mirror databases

1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)

I do not know how this happen

Someone implemented a database mirroring session




lescobar (7/30/2014)
How do I get the database 2 back to show secondary and get rid of restoring ?



Failover or remove the session

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
GilaMonster
GilaMonster
SSC Guru
SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)

Group: General Forum Members
Points: 233377 Visits: 46361
lescobar (7/30/2014)
Hello everyone

I have two sql servers
It is setup as a mirror databases

1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)


Nothing wrong there. That looks like a mirroring set working perfectly. The mirror is *supposed* to be restoring and inaccessible.

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


HanShi
HanShi
SSCrazy Eights
SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)

Group: General Forum Members
Points: 8912 Visits: 3718
The mirrored databases are there for disaster purposes. When the principal database/server goes down you could (manually or automatically when configured) failover. At that moment the partner database will come out of restoring state and will be available. This configuration will minimize donwtime and data loss.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
lescobar
lescobar
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 53
so how do I stop or correct this error message?

Failure Reason:
ERROR CODE [30:325]: Error encountered during backup. Error: [Database "VIEWCOMPOSERDB' cannot be opened because it is offline. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.] Source: shdnapvc01, Process: SQLiDA
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)

Group: General Forum Members
Points: 98380 Visits: 38996
lescobar (7/31/2014)
so how do I stop or correct this error message?

Failure Reason:
ERROR CODE [30:325]: Error encountered during backup. Error: [Database "VIEWCOMPOSERDB' cannot be opened because it is offline. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.] Source: shdnapvc01, Process: SQLiDA


You don't. You can't run backups or log backups against the mirror database. You have to run those against the principal database.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)

Group: General Forum Members
Points: 68701 Visits: 18570
Disable the jobs on the mirror that are trying to perform the backups (or other maintenance). Those should only be enabled in the event of a failover.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

HanShi
HanShi
SSCrazy Eights
SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)SSCrazy Eights (8.9K reputation)

Group: General Forum Members
Points: 8912 Visits: 3718
SQLRNNR (7/31/2014)
Disable the jobs on the mirror that are trying to perform the backups (or other maintenance). Those should only be enabled in the event of a failover.

You could build some logic inside the backup process to skip inaccessable databases. Apply this logic on both the principle and the partner, so a backup of your database is always created.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
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