Exchange Cluster IP address goes walkabout
A power outage at the weekend caused unscheduled shutdowns on our servers. All came back OK and were working fine. However our backup of the Exchange 2010 server failed as Backup Exec could not connect to the Database. We have a DAG set up to a DR site, we failover manually if required and for when we need to do maintenance, it all works rather well. DAGs have an IP address assigned to them which is actually related to the Windows Cluster service, which if the servers are in different subnets have be different depending on which server is active. I believe this is controlled by the Cluster service, Exchange then updated DNS to point to the new server when you move to a different active server. Unfortunately despite not having auto failover the cluster service moved the IP address, Exchange, however, did not update DNS as the active DB had not moved. Bringing the server back up didn't change anything. So we now had the cluster IP address in the DR site and the DB on the productio...