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 12»»

Multiple endpoint on one witness server(Mirroring), Is it possible? How? Expand / Collapse
Author
Message
Posted Wednesday, November 3, 2010 7:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 3, 2011 1:36 PM
Points: 4, Visits: 16
I have 3 database mirroring from different servers.

Can I use only 1 witness SQL server with multiple tcp endpoint? if yes,How?
Or What should I do to handle this situation? Separate witness sql server for each pair looks over kill for me.

I found it can use as witness for only 1 pair. If I try it on the second pair, it cut the witness out from first pair and left database as "Principle, Suspended"

Any help will be really appreciated.

Thank you in advance.
Post #1015210
Posted Wednesday, November 3, 2010 7:53 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: Tuesday, June 24, 2014 12:24 PM
Points: 514, Visits: 1,717
we have 1 witness 'server', but each pair it monitors is a seperate instance.

so we have 6 database servers that are mirrored. (12 seperate servers)
we have 1 witness server with 6 instances running.

everything runs great.
Post #1015223
Posted Wednesday, November 3, 2010 8:19 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 3, 2011 1:36 PM
Points: 4, Visits: 16
Thank Geoff
Is it possible to do something like 1 SQL server instance, 6 TCP endpoints?

Post #1015251
Posted Wednesday, November 3, 2010 8:28 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: Tuesday, June 24, 2014 12:24 PM
Points: 514, Visits: 1,717
no.
but you might be able to do something like;

instance pair 1 mirroring on port 5023
instance pair 2 mirroring on port 5024
instance pair 3 mirroring on port 5025

the witness instance has 1 endpoint all on port 5022

on each of the principal servers, run;
ALTER DATABASE <DATABASE_NAME>
SET WITNESS =
' TCP :// < system-address of the witness server > : 5022'
GO

however, the seperate instance on the witness will lead to a better solution imho....
Post #1015260
Posted Wednesday, November 3, 2010 10:17 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 3, 2011 1:36 PM
Points: 4, Visits: 16
Thank you so much.

For the second pair, I need to do mirroring in High Performance operating mode (change port as your reply) and add Witness as your reply on Principal later, everything comes out perfect.


Thank again.
Post #1015402
Posted Tuesday, May 17, 2011 1:52 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 11:15 AM
Points: 12, Visits: 99
I am also trying to setup Mirroring with failover, the witness instance is on the same server as the mirror instance. My mirror has the default instance name, and my witness is named SQLWitness. How do I specify the following command, it will not allow me to name the instance.

ALTER DATABASE MainDB
SET WITNESS = 'TCP://MirrorDB\SQLWitness:5033';
GO
Post #1110570
Posted Wednesday, May 18, 2011 8:35 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, July 25, 2014 10:16 AM
Points: 1,612, Visits: 1,537
Melissa, you have the slash going the wrong direction. Should be / instead of \.

SET WITNESS = 'TCP://MirrorDB\SQLWitness:5033';




My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server 2008
Principal DBA: Outerwall, Inc.
Also available for consulting: SQL DBA Master
Post #1111028
Posted Wednesday, May 18, 2011 8:39 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 11:15 AM
Points: 12, Visits: 99
I'm almost certain I tried the forward slash.... but I will give it another try. Is there examples of this in the book you recommended?
Post #1111034
Posted Wednesday, May 18, 2011 8:55 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, July 25, 2014 10:16 AM
Points: 1,612, Visits: 1,537
Yes, there are examples and much, much more in the book I wrote. :)



My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server 2008
Principal DBA: Outerwall, Inc.
Also available for consulting: SQL DBA Master
Post #1111064
Posted Wednesday, May 18, 2011 9:12 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 11:15 AM
Points: 12, Visits: 99
When trying this command,

ALTER DATABASE SharePointDB
SET WITNESS = 'TCP://MirrorDB/SQLServerWitness:5033';
GO

I get the following error...

Msg 1449, Level 16, State 5, Line 1
ALTER DATABASE command failed due to an invalid server connection string.

Post #1111082
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse