April 10, 2017 at 12:05 am
Comments posted to this topic are about the item Step by Step Configuring a Dedicated Network for Availability Group
Regards,Ganapathi varma, MCSAEmail: gana20m@gmail.com
April 10, 2017 at 12:58 am
Hi Admin team,
Link is not working. Please fix it.
Regards,Ganapathi varma, MCSAEmail: gana20m@gmail.com
April 10, 2017 at 6:01 am
Thanks very much for the article. Very timely for me.
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
April 11, 2017 at 1:37 am
Br. Kenneth Igiri - Monday, April 10, 2017 6:01 AMThanks very much for the article. Very timely for me.
Glad you liked it 🙂
Regards,Ganapathi varma, MCSAEmail: gana20m@gmail.com
April 11, 2017 at 12:17 pm
Good attribute but needs to cover a bit more in depth especially around DNS.
My stairway level on mirror traffic segregation can be found at this link
http://www.sqlservercentral.com/articles/always+on/131901/
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 25, 2019 at 8:30 am
will this work for 2 NIC configuration? One Public and one heartbeat? I am attempting to move all replication traffic to the Heartbeat NIC which happens to be on a separate vLAN.
SQL Padre
aka Robert M Bishop
"Do or do not, there is no try" -- Yoda
August 12, 2019 at 11:04 am
Hi there,
This will work for your case. I would not recommend using the HB nic for replication traffic if you are using this NIC for cluster nodes for private communication. If you consume entire bandwith for replication traffic and it might effect missing heartbeats between nodes and causes failover.
Regards,Ganapathi varma, MCSAEmail: gana20m@gmail.com
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply