March 31, 2009 at 10:51 pm
I have 2 SQL servers and I am going to mirror from A to B (the witness will be on A - I know, not preferred). I have 2 direct connections between the servers, and the servers also have multiple connections to switches and the internet. I want to ensure that all SQL mirroring happens over the direct connections. I think I can force all traffic onto one direct connection by specifying IP addresses in the "alter database... set partner" commend, but what if I want the second connection to be a failover? How can I force mirroring to use a set of direct connections.
I tried changing the bindings to that these NICs had highest priority, giving them a specific DNS suffix and putting their IP to name.suffix mapping in the hosts file. This seems to work fine when pinging - the one with the highest interface metrix gets the traffic, and if it goes down the other connection gets the traffic. But when I try to use these name.suffix-es in the mirroring commands, SQL changes them to the FQDN of the computer and the traffic doesn't go over the direct connections - it goes via the switches.
The only other thing I can think of is to team the direct connections and then use the specific IP in the mirroring commands. Is teaming reliable or hard to set up?
Can anyone think of any other options to force SQL to use a specific set of connections for mirroring?
Thanks,
-Kim
April 2, 2009 at 10:46 am
NIC Teaming should work. I have used it reliably for a number of years although not in this specific situation. We used to have two teams (4 NICs). One team to the primary core switch A and the other team to backup core switch B.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply