Advertisement

[x]
Attachment Details

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

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.4
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.
Related Solutions
Related Solutions
 
Loading Advertisement...
 
Accepted Solution by lordicarus:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
Loading Advertisement...
20080924-EE-VQP-41 / EE_QW_2_20070628