New answers tagged failover
Yes, it is perfectly possible. Using heartbeat, for example, one might say in ha.cf bcast eth2 where eth2 is the private interface to the heartbeat pair. Communication between the two for the purposes of deciding who's primary will then take place on that interface. That said, I'm curious about your statement that I'm looking for the proper ...
That doesn't make sense. A reboot of one of your Hyper-V hosts should trigger a migration of any clustered VM's on that host to the other Hyper-V host. If the VM's are not clustered then you're seeing the expected behavior. Failover Clustering won't migrate a VM that isn't clustered. If you want those VM's to be migrated then you'll need to cluster them.
DFS answer you. You can create advanced scenario with DFS and clustering too. Like seen there Configuring high availability for the DFS Replication service In this section, we take a look at the steps required for configuring a highly available file server on this newly created failover cluster. As a result of these steps, the DFS Replication ...
Probably not the answer your are looking for but more of a suggestion when dealing with VoIP. After dealing with DNS headaches, route propagation issues and split brain issues, I would strongly suggest looking to your PBX vendor for a solution at that layer and let your endpoints know they have multiple ways to get dialtone. This way you are not dependent ...
For Exchange 2010 you need to create a CAS array, that will handle incoming user traffic, there are some additional settings required. Detailed explanation here.
It depends on your particular requirements. For example, if the application isn't resource intensive you could perhaps go virtual and use VMWare Fault Tolerance. If resource intensive and/or physical you should probably look at DRBD. Hope this helps.
You're going the wrong way about this. What you want to achieve is some sort of HA (high availability). I suggest you look into HAproxy. With its simple configuration, that's all you really need, there are plenty of tutorials out there. You can have two servers as the backends, and they can even share the load between themselves. You sync the files that can ...
With regards to DNS Failover you should understand that normal DNS servers have no method for this. They don't monitor a server, but can simply provide multiple IP's in response to a request (called DNS Round-Robin). The client picks one at random, and if that host is down it may or may not retry the other. It's more of a dumb load-balancing method. Some DNS ...
Top 50 recent answers are included