Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

What are some of the industry standard enterprise software to allow fail-over or swap-over between 2 servers?

E.g., if 1 server goes down(due to connection or power, etc), the other kicks in either immediately, or after a certain time of like a few mins

I have 2 Windows Server 2012 servers, and 2 Windows Server 2008R2 servers. What software should I consider for each of the setup?

share|improve this question

closed as primarily opinion-based by ceejayoz, mdpc, Dave M, kce, faker Jul 31 '13 at 20:02

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

    
It really depends on what service you are trying to protect as to which solution you should be using. What are you trying to protect? –  mrdenny Jul 31 '13 at 15:57

2 Answers 2

up vote 2 down vote accepted

You can use Network Load Balancing (NLB), it's built in Windows, and works with standard version.

You will end with a virtual IP Address, to which client will connect.

It's IP based, so it won't detect if your web server or application stop. It will spread load against all servers until one of them is disconnected from network or dead.

You can use affinity to keep client connected on same node (hash between IP of client and virtual)

It may require special configuration on your switch, depend on setup your will choose (unicast vs multicast).

Technet article

If you also need to share data (shared windows disk through san), then you must look on Windows Failover Clustering. It's more advanced (using resource) , but need a shared storage solution.

Then you can also look for third party solution like Double take, Safekit & co.

You badly defines your needs. You choose a solution based on what will the servers hosts (web sites, mailboxes, dns, databases, custom app...).

Mainly, the solution should be designed to work in high availability, else you will experience issue and won't be supported by the software vendor in case of issue or questions.

share|improve this answer

Windows Server offers this natively, it's called Microsoft Cluster Services.

/edit : Mathieu makes the good point that you might do just fine with MS NLB, depending on the service(s) that you're trying to make highly available.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.