Linux Project
-
@scottalanmiller said:
Truly identical you do with DRBD.
Didn't want to do anything that highend. A once daily sync would be fine, I just don't want the site to be down. Since I am using wordpress could I just sync the DB? Any maybe sync the files using rSync?
-
@Aaron-Studer said:
@scottalanmiller said:
Truly identical you do with DRBD.
Didn't want to do anything that highend. A once daily sync would be fine, I just don't want the site to be down. Since I am using wordpress could I just sync the DB? Any maybe sync the files using rSync?
You could setup a cron job to take a wordpress backup and a cron job on the second one to import the backup. Not the most elegant way to do it though.
-
@Aaron-Studer said:
@scottalanmiller said:
Truly identical you do with DRBD.
Didn't want to do anything that highend. A once daily sync would be fine, I just don't want the site to be down. Since I am using wordpress could I just sync the DB? Any maybe sync the files using rSync?
Then Rsync. The answer is always Rsync with UNIX.
-
Remember that a database has its files open, always. So you can't sync them. You have to backup and restore them. Nothing can sync an open file.
-
@scottalanmiller will rsync ruin my DB?
-
-
If you want a full-on MySQL cluster...
-
So in that case it would be a 2 part job, 1 sync WP directory. 2 backup \ restore DB?
-
@Aaron-Studer said:
So in that case it would be a 2 part job, 1 sync WP directory. 2 backup \ restore DB?
You can do it that way.... three steps...
- Backup
- Sync
- Restore
-
You could do something like this and have it store to something both can access: http://jamieflarity.com/computers/how-to-backup-your-wordpress-database-and-files-without-a-plugin/ then just do a cronjob to import the sql.gz on the second server
-
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.
