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

Database Mirroring Problems Expand / Collapse
Author
Message
Posted Tuesday, October 21, 2008 12:03 PM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 10:16 PM
Points: 158, Visits: 774
Hi all..

I have 2 server in mirroing... this morning i have to boot the mirror server and whens its up the message in mirror database was "restoring..." only.Before the message was something like (restoring, synchronized..etc)..now only "restoring..." . In principal server the message is "principal, synchronized"..but will be synchronized really ?

When i configured this mirroring , this message in target server (only "restoring...") shows up when i restored the dabatase before starts synchronized doing de statments ALTER DATABASE XXX SET PARTNER in principal an target servers.

I try to do this statments agains and shows up a error message

Principal
Msg 1405, Level 16, State 4, Line 1
The database "SM" is already enabled for database mirroring.

Target
Msg 1452, Level 16, State 6, Line 2
The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.


This servers are really synchronized ?


$hell your Experience !!!
Post #589359
Posted Tuesday, October 21, 2008 4:44 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
Check the output of
select * from sys.database_mirroring on principal database and verify whether the configuration is fine and mirroring state is synchronized or Synchronizing.

You can also make use of database mirroring monitor and check the same(by registering your mirroring instances and see whether trafic is there when principal is getting updated).

HTH,
MJ
Post #589506
Posted Wednesday, October 22, 2008 5:32 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 10:16 PM
Points: 158, Visits: 774
Thanks Manu...the select returns in columns

mirroring_state mirroring_state_desc
4 SYNCHRONIZED

for all databases with mirroring

can I presume that everything okay?



$hell your Experience !!!
Post #589713
Posted Wednesday, October 22, 2008 5:52 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
Yes, you can presume that. Also, you can do one thing(if possible) to check this out:

Do a failover when its okie and nobody will get affected. If it goes to mirrored database then it will confirm you to the fullest extent tht all is working fine under the hood.

Manu
Post #589725
Posted Wednesday, October 22, 2008 6:02 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 10:16 PM
Points: 158, Visits: 774
Thanks a lot Manu...


$hell your Experience !!!
Post #589734
Posted Wednesday, June 15, 2011 1:57 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 9, 2013 4:44 PM
Points: 3, Visits: 8
I just spent 2 days trying to figure this out and I got it.

On th Mirror reference the Primary server.

ALTER DATABASE MYDB_04

SET PATNER = 'TCP://PRINCPLESERVERNAME.DOMAIN.LOCAL:PORT#'

On the Primary reference the Mirror server.

ALTER DATABASE MYDB_04

SET PATNER = 'TCP://MIRRORSERVERNAME.DOMAIN.LOCAL:PORT#'

This is not stated correctly in the documentation the I have read.

K9
Post #1126083
Posted Thursday, June 16, 2011 7:09 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 8:53 AM
Points: 4,350, Visits: 6,162
Everyone PLEASE understand that database mirroring is an ADVANCED topic and you REALLY need to study up and practice with it in a test environment before pursuing it. Even better would be to engage a qualified consultant to help you a) understand what you HA/DR needs truly are and b) ensure you get there effectively and c) know how to troubleshoot/resolve issues that might crop up. You might just have your businesses very existence on the line here.

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1126491
Posted Friday, June 17, 2011 2:23 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 18, 2014 3:36 AM
Points: 500, Visits: 294
Hi Laerte

It does sound as though your mirroring configuration is fine. Daft as it sounds, try doing a refresh of the tables in SSMS. This will probably fix the issue regarding not seeing "restoring, synchronized" against each database.

For what it's worth, Kevin is absolutely spot on - mirroring is definitely an advanced topic. I played about in a test environment quite a bit, doing automatic failovers/manual failovers, turning servers off etc to see what would happen. It is not something I would recommend anybody should put into production until you are comfortable you can manage it correctly.

Mike.
Post #1127137
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse