Tag Info

Hot answers tagged

10

Yes, it's a bit old school. Modern hardware doesn't just fail that often. Focus either on making your applications more highly-available (not always possible), or on the items needed to make your individual hosts more resilient... For hosts: Buy better hardware. Ensure you have support contracts. REGISTER your servers' support contracts (spare parts are ...


7

It's rather inefficient - not least because of the dependency on manual intervention to make the switch. I have worked at places that run a hot DR site - literally, identical servers to the primary, ready to go instantly. However the DR switchover is an automated process - we're not talking cabling, a bit of fiddling and a switch, but a process when we ...


4

The fact that it is old school doesn't necessarily make the use of a hot spare a bad idea. Your main concern should be the rationale, what are the risks you run, and how does running a hot spare mitigate them. Because in my perception your hot spare only addresses hardware failure, which is although not uncommon, neither the only operational risk you run, ...


4

Sobrique explains how the manual intervention causes your proposed solution to be sup-optimal, and ewwhite talks about probability of failure of various components. Both of those IMO make very good points and should be strongly considered. There is however one issue that nobody seems to have commented on at all so far, which surprises me a little. You ...


2

The concept of having a hot or even cold spare is dependent how the application(s) are built in the first place. What I mean is that if the application has been built in such a way that the data and service load is spread across multiple machines then the concept of any single machine taking the system down should go away. In that situation you don't need ...


1

I'm using Tungsten Replicator with 3 MySQL servers across the world (all masters configuration). This configuration is working for me. MySQL.Cluster resolves to virtual IP of "main" node in corosync cluster - it's better to write to only one master :) $wpdb->add_database(array( 'host' => 'MySQL.Cluster', // If port is other than 3306, ...



Only top voted, non community-wiki answers of a minimum length are eligible