by joeclef on 10/9/16, 7:06 PM with 87 comments
by dangrossman on 10/9/16, 7:30 PM
* rsyncs the directories containing the files you want to back up
* mysqldumps/pg_dumps your databases
* zips/gzips everything up into a dated archive file
* deletes the oldest backup (the one with X days ago's date)
Put this program on a VPS at a different provider, on a spare computer in your house, or both. Create a cron job that runs it every night. Run it manually once or twice, then actually restore your backups somewhere to ensure you've made them correctly.
by yvan on 10/9/16, 7:35 PM
We basically create a backup folder (our assets and MySQL Dump, then rsync it to rsync.net). Our source code is already on git, so basically backuped on Github, and all developers computer.
On top of it, rsynch has a very clear and simple documentation to implement it very quickly with any Linux distrib.
by Kjeldahl on 10/9/16, 8:20 PM
by no_protocol on 10/9/16, 10:12 PM
I use tarsnap, as many others in this thread have shared. I also have the Digital Ocean backups option enabled, but I don't necessarily trust it. For the handful of servers I run, the small cost is worth it. Tarsnap is incredibly cheap if most of your data doesn't change from day to day.
by rsync on 10/9/16, 9:38 PM
[1] info@rsync.net
by kumaraman on 10/9/16, 7:43 PM
by stevekemp on 10/10/16, 9:00 AM
My main site runs a complex series of workers, CGI-scripts, and deamons. I can deploy them from scratch onto a remote node via fabric & ansible.
That means that I don't need to backup the whole server "/" (although I do!). If I can setup a new instance immediately the only data that needs to be backed up is the contents of some databases, and to do that I run an offsite backup once an hour.
by AdamGibbins on 10/9/16, 7:34 PM
by xachen on 10/9/16, 7:31 PM
by touch_o_goof on 10/9/16, 9:50 PM
by bretpiatt on 10/9/16, 8:01 PM
For a database driven dynamic site or a site with content uploads you can also use your version control via cron job to upload that content. Have the database journal out the tables you need to backup before syncing to your DVCS host over choice.
If you're looking for a backup service to manage multiple servers with reporting, encryption, dedupelication, etc. I'd love your feedback on our server product: https://www.jungledisk.com/products/server (starts at $5 per month).
by billhathaway on 10/9/16, 9:25 PM
Lots of people only do a full test of their backup solution when first installing it. Without constant validation of the backup->restore pipeline, it is easy to get into a bad situation and not realize it until it is too late.
by darkst4r on 10/10/16, 2:08 AM
by pmontra on 10/9/16, 8:51 PM
OVH has a backup by FTP premium service but the FTP server is accessible only by the VPS it backups. Pretty useless because in my experience if an OVH VPS fails the technical support has never been able to take it back online.
by jasey on 10/10/16, 5:56 AM
[1]http://duplicity.nongnu.org/
http://mindfsck.net/incremental-backups-amazon-s3-centos-usi...
by jenkstom on 10/10/16, 1:18 PM
by Osiris on 10/10/16, 5:13 AM
For database, I use a second VPS running as a read only slave. A script runs daily to create database backups on the VPS.
by 2bluesc on 10/9/16, 7:43 PM
Make sure you check the status of backups, I send journald and syslog stuff to papertrail[0] and have email alerts on failures.
I manually verify the back-ups at least once a year, typically on World Back-up Day [1]
[0] https://papertrailapp.com/ [1] http://www.worldbackupday.com/en/
by spoiledtechie on 10/9/16, 7:38 PM
Stupid simple and stupid cheap. Install, select directories you want backed up, set it and forget it.
All for $7.00 a month.
by stephenr on 10/10/16, 5:39 AM
Collect your files, rsync/scp/sftp them over.
Read only snapshots on the rsync.net side means even an attacker can't just delete all your previous backups.
by aeharding on 10/9/16, 8:49 PM
I just use a simple scheduled AWS lambda to PUT to the redeploy webhook URL.
I use an IAM role with put-only permissions to a certain bucket. Then, if your box is compromised, the backups cannot be deleted or read. S3 can also be setup to automatically remove files older than X days... Also very useful.
by geocrasher on 10/9/16, 7:54 PM
by colinbartlett on 10/9/16, 8:09 PM
by mike503 on 10/10/16, 12:22 AM
Then the script sends it to s3 using aws s3 sync. If versioning is enabled you get versioning applied for free and can ship your actual data and webdocs type stuff up extremely fast and it's browsable via the console or tools. Set a retention policy how you desire. Industry's best durability, nearly the cheapest too.
by kevinsimper on 10/10/16, 11:38 AM
by dotancohen on 10/10/16, 5:16 AM
by extesy on 10/9/16, 8:49 PM
by benbristow on 10/9/16, 7:39 PM
by moreentropy on 10/10/16, 6:30 AM
I can't praise restic enough. It's fast, secure, easy to use and set up (golang) and the developer(s) are awesome!
by wtbob on 10/10/16, 12:26 AM
by educar on 10/9/16, 9:21 PM
by 00deadbeef on 10/9/16, 9:12 PM
by bedros on 10/10/16, 9:24 PM
by voycey on 10/10/16, 6:35 AM
by ausjke on 10/10/16, 4:47 AM
by yakamok on 10/9/16, 9:13 PM
by edoceo on 10/9/16, 11:26 PM
Use pg_dump and tar then just s3cp
by chatterbeak on 10/9/16, 8:47 PM
All the databases and other data are backed up to s3. For mysql, we use the python mysql-to-s3 backup scripts.
But the machines themselves are "backed up" by virtue of being able to be rebuilt with saltstack. We verify through nightly builds that we can bring a fresh instance up, with the latest dataset restored from s3, from scratch.
This makes it simple for us to switch providers, and can run our "production" instances locally on virtual machines running the exact same version of CentOS or FreeBSD we use in production.
by X86BSD on 10/10/16, 5:04 AM
If you're not using a modern Unix variant with ZFS... well there isn't a good reason why you would be.
by nwilkens on 10/9/16, 7:56 PM
You can also use https://r1softstorage.com/ and receive storage + R1soft license (block based incremental backups) -- or just purchase the $5/month license from them and use storage where you want.