MarkMichael
asked on
Exchange 2010 - Failover Clustering - Disable backup nic from causing a failover
Hi Experts,
On Exchange 2007 with Failover Clustering, we would go into the failover cluster manager and disable the backup NIC in the policy to allow it to cause a failover.
With the servers we have, they are highly available (dual NICs for ALL connections going onto 2 switches to ensure the highest uptime as possible).
We would normally disable the backup nic from being able to cause a failover, as the backup network only has a single NIC with a single switch for this purpose.
Is there a setting to disallow the NIC from causing a failover for Exchange 2010?
On Exchange 2007 with Failover Clustering, we would go into the failover cluster manager and disable the backup NIC in the policy to allow it to cause a failover.
With the servers we have, they are highly available (dual NICs for ALL connections going onto 2 switches to ensure the highest uptime as possible).
We would normally disable the backup nic from being able to cause a failover, as the backup network only has a single NIC with a single switch for this purpose.
Is there a setting to disallow the NIC from causing a failover for Exchange 2010?
you need to ensure that the nic is not being used for public communication, otherwise it will cause an interruption that will cause a failover
ASKER
This being the tickbox of 'clients can connect through this network'?
If i disable that, the backup server will not be able to communicate to Exchange?
If i disable that, the backup server will not be able to communicate to Exchange?
if you disable that, then the network is only used for replication traffic
ASKER
but I need to use it for backup?
Sorry, I'm confused.
Sorry, I'm confused.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah, do I just remove it as a resource?
It looks to be automatically added when I set the clustering up.
It looks to be automatically added when I set the clustering up.