isoperations
asked on
1gb host becoming saturated when writing to 10gb host.
Hello,
I have a situation that I am not 100% sure how to resolve. I have a Windows host, Host A, that has a 1 gig connection to the core and is part of a Windows cluster. I have another host, Host B, that has a 10gig connection to the core. Host B is essentially a NAS and a target for disk-2-disk backup. Host A is a SQL Active/Passive cluster. The problem I have is when Host A runs its backup dumping to Host B it saturates Host A's link and causes the cluster to failover becuase SQL/Windows Clustering thinks it has lost network connectivity. I have enabled flow control on both ports and ensured it is enabled on both interfaces or both hosts. The only solution I can come up with is to setup some type of rate limiting. Does anyone have any other thoughts?
Thanks in advance!
I have a situation that I am not 100% sure how to resolve. I have a Windows host, Host A, that has a 1 gig connection to the core and is part of a Windows cluster. I have another host, Host B, that has a 10gig connection to the core. Host B is essentially a NAS and a target for disk-2-disk backup. Host A is a SQL Active/Passive cluster. The problem I have is when Host A runs its backup dumping to Host B it saturates Host A's link and causes the cluster to failover becuase SQL/Windows Clustering thinks it has lost network connectivity. I have enabled flow control on both ports and ensured it is enabled on both interfaces or both hosts. The only solution I can come up with is to setup some type of rate limiting. Does anyone have any other thoughts?
Thanks in advance!
Do you have any possibility to prioritze the heartbeat packets or even better: do you have the possiblity to let the heartbeat run over a separate link?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.