Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2008-06-12
1
Medium Priority
?
744 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

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Question has a verified solution.

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

Recently, when I was asked to create a new SQL 2005 cluster, Microsoft released a new service pack for MS SQL 2005 what is Service Pack 3. When I finished the installation of MS SQL 2005 I found myself troubled why the installation of SP3 failed …
In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…

688 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