11–20 of 21 posts
For our "internal" stuff: * Monthly whole drive snapshots to an external HD * Daily Time Machine backups to an external HD * Everything backed up continually with CrashPlan * All work stuff synced continuously in DropBox * Monthly restore-a-random-file test to sanity check
Are your whole drive snapshots deduplicated?
I've got the client side script tweaked so that you can run it as a standalone setup (backup to a local USB drive), or backup to a remote Linux server via a non-privileged account, or have the remote backup server pull backups from your clients. The features that are currently in development for the next version include client-side encryption, and pluggable backend replication, so you can replicate your backup sets to cloud providers, or tape, or to another Snebu installation.
I can definitely use some more feedback, probably need to do another round of documentation improvements, but overall the code seems quite stable. The project sites is up on github (github.com/derekp7/snebu) if you are interested in contributing.
Earlier quoted context omitted.
Yes, exactly. The client source is available too if you like, though it's not really free software since the license still only allows you to use it with the official Tarsnap service.
Sounds useful, I need to look for FOSS software that can do the same for local storage targets.
My code syncs to Dropbox. All of my projects (even experiments) are committed to private Github repos. I have two machines, so Dropbox essentially creates a physical backup on my secondary machine, which is nice. I also have scheduled backups to an external drive, which enables file history as well. So for me to lose my files, my main machine, my secondary machine, my external drive, Github, and Dropbox would all hav…
Thanks - so your code lives both on Dropbox and Github? Also - you probably ln -s'd your workspace folder to your Dropbox folder?
I don't actually know how Dropbox does with symlinks. I just put my workspace folder in my Dropbox folder.
The key is to keep it simple and easy.
Earlier quoted context omitted.
Thanks - so your code lives both on Dropbox and Github? Also - you probably ln -s'd your workspace folder to your Dropbox folder?
Every single time I hit save, Dropbox saves another copy of the file, so I have a complete file history. Github only has the commits. I don't actually know how Dropbox does with symlinks. I just put my workspace folder in my Dropbox folder.
I'm scared to back up the bulk of my data because I don't want to put it on dropbox or s3 because they could get hacked or otherwise divulge to law enforcement. And encrypting it all first is a pain.
Right now I only do a local backup to a usb HD. However, I'm considering getting an amazon EBS volume and setting up a Ruby script or something to put up a micro server, compress and encrypt my files and sent them out the the aws volume.
Backblaze/crashplan is cheaper, but they use a server side key, which is pretty pointless. Glacier would be cheaper but seems more complicated to set up.
I have cloud services for anything I share with clients or friends but I honestly don't trust them for anything critical. I actually back up Dropbox to the NAS too. Problem being that the sync strategy across multiple clients can wipe a folder shared between them. It's also a beast to recover from a cloud backup
The trick I'm most proud of is at the end of each year I buy a new external backup drive (now NAS), copy the old one to the new drive, and then label the old drive with the year and store it somewhere safe. It costs a few $$ each year to archive the drives but well worth it - they have saved my butt more than once. I also buy a new laptop workstation every 2 years or so and preemptively migrate everything to the new machine before the old machine dies, and keep the old one around as a spare.
I can't recommend Tarsnap ( https://www.tarsnap.com/ ) enough for personal backups for hacker-types. Everything is encrypted client-side, so don't lose you key or thee is literally nothing you can do to get at your data again. It's also deduplicated and compressed so you can do snapshots often (on my machines I have a cron that runs every six hours) without going broke since (similar to git) you're only storing chang…
However, for things like photos the cost (as little as Colin charges) start to really add up. I do my photos on Apple and recently dumped my library into iCloud (offsite backup I guess) and then I periodically rsync that to my NAS. Photos are also backed up to Time Machine on a separate disk. I figure this gives me a fair bit of redundancy and covers me if iCloud deletes all my photos too.
I've tried to do the Time Machine disk shuffling (swapping disks between home and office) but if it's not automated, it doesn't happen.
I'm scared to back up the bulk of my data because I don't want to put it on dropbox or s3 because they could get hacked or otherwise divulge to law enforcement. And encrypting it all first is a pain.
Similar here, don't really want to do a full backup of all my personal files and such to dropbox. Right now I only do a local backup to a usb HD. However, I'm considering getting an amazon EBS volume and setting up a Ruby script or something to put up a micro server, compress and encrypt my files and sent them out the the aws volume. Backblaze/crashplan is cheaper, but they use a server side key, which is pretty poin…