Solved

Proper configuration for database mirroring with witness and crossover cable for mirroring traffic

Posted on 2008-06-12
1
742 Views
Last Modified: 2008-06-12
I am trying to setup a server with database mirroring in SQL 2005, but I need to have the mirroring traffic go over a crossover cable between the principal and the mirror.  DNS has an entry for the principal and mirror for these mirror interfaces so that they can see each other.

Principal - 3 NICs - Public, Private, Mirror
Public x.x.x.x, Private 10.10.1.101 (DB1.DOMAIN.LOCAL), Mirror 192.168.0.101 (DB1-DBM.DOMAIN.LOCAL)

Mirror - 3 NICs - Public, Private, Mirror
Public x.x.x.x, Private 10.10.1.102 (DB2.DOMAIN.LOCAL), Mirror 192.168.0.102 (DB2-DBM.DOMAIN.LOCAL)

Witness - 2 NICs - Public, Private
Public x.x.x.x, Private 10.10.1.103 (DBWITNESS.DOMAIN.LOCAL)



Do I need to add a third NIC to the witness to allow the witness to do its job?

If I do _not_ need a third NIC, what settings would I use when I "Configure Security" in the Mirroring setup to ensure that the witness will do it's job?  It seems like if I use the DB1-DBM and DB2-DBM in the settings, the witness will never be able to communicate with them since it does not have access to the 192.168.0.x network.
0
Comment
Question by:lordicarus
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 2

Accepted Solution

by:
lordicarus earned 0 total points
ID: 21773984
Actually I figured this one out.  In reality you _could_ set this up by creating a reference in the hosts file on the witness server to point db1-dbm and db2-dbm to the 10.x addresses, and it would be able to tell if the servers were up and sql was responding, but since it's not on the same 192 network it doesn't ensure that db1 and db2 are actually able to communicate over said crossover.  

The solution would be to put the three servers on their own VLAN and add a third NIC to the witness server.  Third nic would be required since repurposing the public or private nic as the dbm connection would not be allowed (due to client needs) and since the issue with doing something like the hosts file thing would still be an issue if it wasnt connected to the same vlan.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When writing XML code a very difficult part is when we like to remove all the elements or attributes from the XML that have no data. I would like to share a set of recursive MSSQL stored procedures that I have made to remove those elements from …
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question