Whats your backup plan for production sites?

[vpsnewb]

Curious to learn what others here do for backups for their production sites.

I've got a cron that runs every 30 minutes to backup the DB offsite to another VPS with another provider and the WWW directory every 2 hours. I feel this is sufficient and it's nice knowing that in a 'shit hits the fan' type scenario a current backup is available to get things back up and running again quickly.

What about you all? Do you have a proper backup plan in place?

 

[drmike]

2 hours is fine if not too busy.

Database backups are a problem since no simple way I know of to deal with updates.   You could develop a non-update database model and deal with linear point in time incrementals.

Currently, no big solution on my side for database since I have over 200GB database to deal with.

At base, I do rsync to remote locations at 15 minute intervals.   Only the new/changed files.  Takes a few minutes to run since we have a few hundred thousand files and nested directories to compare.

 

[HalfEatenPie]

I know KuJoe has one of the best backup setups that just can't be beat!

Personally (as in, unrelated to Catalyst), my most important files are rsynced to three VPSes each with different providers and my dedicated backup server nightly.  That and constant monitoring is all I really do.  

Of course, those "important" files are more personal files I need and use on a daily basis.  

 

[KuJoe]

I know KuJoe has one of the best backup setups that just can't be beat!

Personally (as in, unrelated to Catalyst), my most important files are rsynced to three VPSes each with different providers and my dedicated backup server nightly.  That and constant monitoring is all I really do.  

Of course, those "important" files are more personal files I need and use on a daily basis.  

Actually this isn't true anymore. We no longer utilize a web cluster like we had before. We just use a single VPS with backups now.

 

[Ruchirablog]

I just remote desktop to my Ramnode cached vps and download the files. too lazy to automate

 

[jhadley]

Idera/R1soft every hour

 

[wilbo]

My important sites are on a vps, then I have a backup vps at another datacenter that is an exact copy.  If one goes down I just have to change the IP numbers of the nameserver at my registrar and then everything goes to the backup vps.  My sites don't use many databases except for counters,  so everything will work fine.  I know this is not the correct way to do it,  but it works for me.

 

[wilbo]

double post

 

[willie]

Database backups are a problem since no simple way I know of to deal with updates.   You could develop a non-update database model and deal with linear point in time incrementals.

Currently, no big solution on my side for database since I have over 200GB database to deal with.

Usually one handles this with replication and journaling.  Depending on what you're doing you might consider a distributed, redundant db like Mongo or Cassandra or Riak.

 

[LusoVPS]

I do Hourly database backups. The files from www are backed up every month, after all, these are static files.

Regards

 

[libro22]

Twice a day backup on remote server. The plan is to backup on another remote server for retention, but I haven't setup the 2nd server yet. It's just sitting there.