Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Mirror database stuck-in-restoring-state Expand / Collapse
Author
Message
Posted Wednesday, July 30, 2014 9:30 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 18, 2014 9:31 AM
Points: 3, Visits: 21
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 ?


Post #1598079
Posted Thursday, July 31, 2014 12:01 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:41 PM
Points: 6,760, Visits: 14,413
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"
Post #1598095
Posted Thursday, July 31, 2014 6:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:22 AM
Points: 40,632, Visits: 37,094
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 2008, MVP
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

Post #1598215
Posted Thursday, July 31, 2014 7:38 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 2,482, Visits: 3,025
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’! **
Post #1598263
Posted Thursday, July 31, 2014 10:36 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 18, 2014 9:31 AM
Points: 3, Visits: 21
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
Post #1598374
Posted Thursday, July 31, 2014 11:04 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 2:40 PM
Points: 20,863, Visits: 32,901
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.



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)
Post #1598393
Posted Thursday, July 31, 2014 11:06 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 2:39 PM
Points: 18,064, Visits: 16,108
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
Post #1598395
Posted Thursday, July 31, 2014 1:11 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 2,482, Visits: 3,025
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’! **
Post #1598453
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse