Linux Project
-
Or you could cluster the MySQL instances. It is pretty rare that you would want to protect a system anywhere but at the application level. The idea that you do it somewhere beneath the apps themselves is a notion that vendors like VMware try to push to SMB clients who don't understand that apps needs to replicate themselves and can do so far better than the platform can.
-
Hm..... Just found this....
-
So want I am thinking about doing is running a server at home and on C@C, and having them in sync. then if ether one goes down, no problem.
-
@Aaron-Studer said:
So want I am thinking about doing is running a server at home and on C@C, and having them in sync. then if ether one goes down, no problem.
That mostly makes sense. Dealing with the dynamic IP address of your house is the pain. But this doesn't explain the DNS thing.
-
How do I setup cloudflare to point to 2 ip addresses?
-
@Aaron-Studer said:
How do I setup cloudflare to point to 2 ip addresses?
Stop. Everything is wrong here. What do you picture you are going to do with two IP addresses here?!?
-
And what do you imagine YOUR DNS servers are going to do?
-
So I am going to have 2 IP addresses - one Public IP address from C@C and One Public IP from my home internet. How do I setup my domain in such a way that it trys C@C first, and if that does loads, loads my home server?
-
@Aaron-Studer said:
So I am going to have 2 IP addresses - one Public IP address from C@C and One Public IP from my home internet. How do I setup my domain in such a way that it trys C@C first, and if that does loads, loads my home server?
DNS does not do that. To do what you are picturing you need a load balancer like an F5 or HAProxy. DNS doesn't do this, ever. You are using the wrong tools and the wrong approach. If you want failover for webservers, you are getting into a whole new level of complexity. A huge one. Even after we fix this layer, you have to fix things like database sync when the system fails back and forth!!
What you want is CloudFlare, don't even think of ever running your own DNS servers. No one should ever do this. Not in the SMB, not the Fortune 101, no one. DNS points to your main IP. If your site fails, manually switch the IP to your backup. That's about the best you are going to get.
-
If you wanted failover, you would buy a bunch of VMs at AWS or Rackspace. Then buy a load balancer. Have the load balancer detect if one of the VMs fails. Then it would point to the other one. I manage load balancers at Rackspace for this all of the time.
-
@scottalanmiller said:
@Aaron-Studer said:
So I am going to have 2 IP addresses - one Public IP address from C@C and One Public IP from my home internet. How do I setup my domain in such a way that it trys C@C first, and if that does loads, loads my home server?
DNS does not do that. To do what you are picturing you need a load balancer like an F5 or HAProxy. DNS doesn't do this, ever. You are using the wrong tools and the wrong approach. If you want failover for webservers, you are getting into a whole new level of complexity. A huge one. Even after we fix this layer, you have to fix things like database sync when the system fails back and forth!!
What you want is CloudFlare, don't even think of ever running your own DNS servers. No one should ever do this. Not in the SMB, not the Fortune 101, no one. DNS points to your main IP. If your site fails, manually switch the IP to your backup. That's about the best you are going to get.
I see. Updates to IP addresses in CloudFlare are very fast, so changing the IP should work, with minimal downtime. At lease I would have options, and not be completely screwed.
-
@Aaron-Studer said:
I see. Updates to IP addresses in CloudFlare are very fast, so changing the IP should work, with minimal downtime. At lease I would have options, and not be completely screwed.
Yes, that's really best. Multi-site failover is a tough thing. You could, in theory, build a system that automatically updated DNS when a failure was detected, but the problems that this would cause are immense, there is a reason that no one does this.
-
@scottalanmiller This is what I was thinking of I think
http://www.gearbytes.com/2010/11/configuring-dns-round-robin-in-windows-dns-for-load-balancing/
-
With Active-Passive I've only done it manually. for Automated you'd usually have Active/Active with loads of nodes both for failover and load-balancing. Unless it's a e-commerce or other money generating site it's not worth it.
-
P.S. Now I feel stupid.
-
@Aaron-Studer said:
@scottalanmiller This is what I was thinking of I think
http://www.gearbytes.com/2010/11/configuring-dns-round-robin-in-windows-dns-for-load-balancing/
Sure, you can do round robin with "any" DNS system. But that would just hose your site as you'd have competing database masters. You'd need a multi-master setup to make that work and it would not help with outages, it would keep sending half of your traffic to the failed site even after it had failed.
-
@Aaron-Studer said:
@scottalanmiller This is what I was thinking of I think
http://www.gearbytes.com/2010/11/configuring-dns-round-robin-in-windows-dns-for-load-balancing/
There are DNS services that will do round robin and detect when a host is down and remove it. The problem is the TTL of the entries isn't always honored. and before that you have no way of making sure traffic goes to your primary host (nslookup doesn't care about the order you put them in on the records)
-
I think that you are over thinking this. Keep things pretty simple. Having two servers and manually failing over from your DNS provider is still far more failover than most sites have.
-
@Aaron-Studer, I've been wanting to do this as well. However, I've moved off AWS so I don't think I'll need to anymore...
-
But Rsync for the Wordpress files and auto-exports and imports of the MySQL databases.
