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

Msg 3013 acting as a mirror database Expand / Collapse
Author
Message
Posted Tuesday, June 11, 2013 6:38 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 03, 2014 8:20 AM
Points: 134, Visits: 1,077
"Database cannot be opened. It is acting as a mirror database.
Msg 3013,
Level 16,"

After restarting the principle & mirror server, my backup jobs are getting the message above.

Is there a way to get by this? Does the cache needs to be flush, do I need to wait whenever the restore/fail over is completed?

Database cannot be opened. It is acting as a mirror database.
Msg 3013,
Level 16,
Post #1462047
Posted Tuesday, June 11, 2013 6:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:15 PM
Points: 5,951, Visits: 12,822
what operating mode are you using for your mirror session?
do you have a witness server?


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1462054
Posted Tuesday, June 11, 2013 7:31 AM


SSC-Insane

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

Group: General Forum Members
Last Login: Yesterday @ 6:33 PM
Points: 22,475, Visits: 30,157
Looks like the backup jobs are running on the wrong server or your principal and mirror databses are active on the wrong servers (meaning what should be your principal database is currently acting as the mirror database just like the error message says).



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 #1462123
Posted Tuesday, June 11, 2013 8:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:15 PM
Points: 5,951, Visits: 12,822
IMHO backup jobs should be running on the mirror, they should at least be intelligent enough to skip databases that are not online.
The mirror may not always be a dedicated mirror you may have other online databases on that instance.


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1462191
Posted Tuesday, June 11, 2013 8:57 AM


SSC-Insane

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

Group: General Forum Members
Last Login: Yesterday @ 6:33 PM
Points: 22,475, Visits: 30,157
Perry Whittle (6/11/2013)
IMHO backup jobs should be running on the mirror, they should at least be intelligent enough to skip databases that are not online.
The mirror may not always be a dedicated mirror you may have other online databases on that instance.


Agreed, but it is apparent that the backup(s) that are failing are failing because the database(s) are active as mirror databases not the principal database(s).

When I configured my databases to use mirroring I had processes in place to enable or disable the backup jobs as appropriate depending on the state of the databases on the servers.

The only backups that were active on both servers were the backup jobs that backed up my system databases. There were no other active user databases on my mirror servers. These were dedicated to provide HA for production databases.



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 #1462200
Posted Tuesday, June 11, 2013 9:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 03, 2014 8:20 AM
Points: 134, Visits: 1,077
Yes I am using a witness server and there are other databases running on the principal which are being backup however they are not mirror like the eight that are not being backup. My witness is acting as the principal now and the principal is being the witness, thats where the backup job are located, on the witness. should I have my backup log jobs running on both Principal and witness?
Post #1462226
Posted Tuesday, June 11, 2013 9:30 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:15 PM
Points: 5,951, Visits: 12,822
You have your topology slightly skewed. The witness does not hold mirrored databases, that's the mirror instance that holds them.

The witness is a third instance that provides quorum in the event of a mirror session failure.

So, are using synchronous or asynchronous mirroring?
Do you have a witness?

The point is you can't manually fail over unless transaction safety is set to Full and the principal is online.


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1462231
Posted Tuesday, June 11, 2013 11:11 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 03, 2014 8:20 AM
Points: 134, Visits: 1,077
Synchronous mode and yes I'm using a witness. When querying the sys.database_mirroring on the Mirror Server it says that the mirroring_role_desc is the Principal, the mirroring_state_desc is SYNCHRONIZING and the mirroring_partner_instance is the ServerA(which was set up as the Principal)
Post #1462275
Posted Wednesday, June 12, 2013 12:24 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:15 PM
Points: 5,951, Visits: 12,822
So you've had a failover then, do you want to fail it back?

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

"Ya can't make an omelette without breaking just a few eggs"
Post #1462470
Posted Wednesday, June 12, 2013 6:23 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 03, 2014 8:20 AM
Points: 134, Visits: 1,077
Yes I to fail it back, which I have done by restarting SQL so now my Principal Server is back to being the Principal but my backup transaction logs are not running they are get the MSG 954, database is acting as a mirror.....
Post #1462584
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse