Hot answers tagged failover
The reason you're frustrated is because you're trying to do something that you shouldn't be doing. You say If anyone is now saying, “wait, what about a SAN or a NAS for the file servers?”, well too bad.` You're right. Too bad for you. What you're trying to do cannot work. A cluster disk must be the same disk shared amongst cluster members. You can't ...
You are right - round robin DNS would not be a solution in this case. What you need is a DNS service that monitors the availability of your servers and switches over the DNS record for the web site to a failover IP once a problem occurs. An example of such a service is DNS Made Easy's DNS failover service.
If you place the load balancing function outside your wan links such that it has its own public ip address(external to your network) to point your clients at, you can configure it to reverse-proxy to services at both your wan link ip addresses. Such a design would make for load balancing and failover without bgp. I guess you could co-locate a redundant load ...
The article you link to sets up one server to act as an iSCSI target that both Hyper-V servers connect to for shared storage (did you not catch that?). Meaning, it acts as the NAS/SAN-like device and provides the shared storage that the other two hosts both connect to for storage. What you are trying to do is completely different. .. Am I even heading in ...
Only top voted, non community-wiki answers of a minimum length are eligible