Solved

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

Posted on 2008-06-12
1
741 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

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
CONVERT date time to a different time zone. 2 79
Error when saving to sql table a '/' 5 32
Addition to SQL for dynamic fields 6 63
Sql Server group by 10 58
Introduction: When running hybrid database environments, you often need to query some data from a remote db of any type, while being connected to your MS SQL Server database. Problems start when you try to combine that with some "user input" pass…
INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

738 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