Backup or not?
A) 1 linode holds php + nginx
B) 1 linode holds mysql
C) 1 linode holds redis
I also have a linode that RSYNCs the content of (A) and mysqldumps every morning from (B) and stores it i.e. in effect creates a backup of my site and stores it on this one linode that does nothing else than just sit there as backup. At times, I even make backup of the backup and RSYNCs the whole linode to my home machine so that if New Jersey gets completely snowed in, I can still setup my site elsewhere with a couple of days lagging.
My simple question is: is there a better/simpler/cheaper way to make backups at linode? I know of the backup package but pardon me for saying so but it seems …. well, not so good.
Anyways, please do feel free to pitch me your suggestions, if you can spare the time.
Much appreciated.
10 Replies
If it's not Web 2.0 (no AJAX for example) then it's still a site, not an app, that's my understanding.
It's tough to do better than rsync for backups, after the very first one, it's fast for daily backups, use the -e option to run over ssh.
If a vulnerability in rsync is ever found then all operating systems are in trouble.
Thanks!
Linode dumps an rdiff-backup incremental to it every night.
Wouldn't recommend that for a mission critical system, but for personal stuff it's fine.
@rsk:
I have an old quiet laptop with a big disk running 24/7 at home.
Which keeps him busy on weekends backing that up to floppies…
@Guspaz:
If a vulnerability in rsync is ever found… it won't matter for most of us, as we don't use rsync in daemon mode. We use it over SSH, and so in order to exploit a flaw in rsync they would first need to get an authenticated SSH connection to the server.
That's true.
I'll take a look into rdiff-backup though! Thanks!