After reading a post from someone who nearly lost all their data to a joint NAS and external hard drive failure I decided to think through my data durability.
Most of my stuff lives in the cloud: email on Gmail, docs in Google Docs, photos in Google Photos, data in Google Drive. I trust Google a lot for this sort of thing, both given their public reputation and as an employee. I think Google is extremely unlikely to lose or corrupt my data.
The next biggest place where I have things is on the server that runs jefftk.com. I back this up to my la…
After reading a post from someone who nearly lost all their data to a joint NAS and external hard drive failure I decided to think through my data durability.
Most of my stuff lives in the cloud: email on Gmail, docs in Google Docs, photos in Google Photos, data in Google Drive. I trust Google a lot for this sort of thing, both given their public reputation and as an employee. I think Google is extremely unlikely to lose or corrupt my data.
The next biggest place where I have things is on the server that runs jefftk.com. I back this up to my laptop with a cronjob that looks like:
rsync -t -l -r -c ps:jtk/ www-jefftk-com/ --delete-after
rsync -t -l -r -c ps:tc/ www-trycontra-com/ --delete-after
rsync -t -l -r -c ps:fr/ www-freeraisins-com/ --delete-after
...
rsync -t -l -r -c ps:kf/ www-kingfisherband-com/ --delete-after
rsync -t -l -r -c ps: ps-rest/ --delete-after
rsync -t -l -r -c ps:/etc/ ps-etc/ --delete-after
This copies each of my websites, the rest of my home directory, and the contents of /etc. It’s set to run once a day, if my laptop is on then, which it is more often than not. It copies them into a subdirectory of ~/Google Drive, which means it then all gets synced to Drive.
I also have a cronjob set up to run twice a month that backs up the comments on my blog posts. It pulls out the /wsgi/json-comments/ urls from my blog posts, fetches them all, and saves them. When Google Plus gets turned off I’m planning to configure my comment system to serve those comments from my backup.
Finally, code lives on GitHub plus local checkouts on my server, laptop, or both.
Everything on my laptop is temporary, and anything important is under ~/Google Drive. All my dotfiles, including my ~/.full_history, are symlinks to into ~/Google Drive.
The main weakness in this setup is its dependency on Drive. Specifically:
For the portion of Google Drive synced to my laptop, if I accidentally deleted or changed things locally that could be synced up. If I noticed right away there’s the Drive Trash which keeps things for 30 days, or I could contact support. Something that corrupted files in a subtle way could be pretty bad.
Very occasionally people have lost access to their Google accounts. For example, by forgetting your password or getting mistaken for a fake account. If this happened to me it would be a disaster: so much of what I use is a Google service.
I think both of these are too unlikely to be worth mitigating though. They could happen, but they’re much less likely than the sort of failure (~1%/year) that you’re trying to avoid by backing things up.
Update 2019-01-26: the day after posting this I spilled water on my laptop, but it was actually fine.
Comment via: facebook, substack
Recent posts on blogs I like:
Inkhaven Blog Recommendations
I was recently a contributing writer at the blogging retreat Inkhaven.
via Thing of Things December 12, 2025
How to Make a Christmas Wreath
Yesterday, I made a Christmas wreath. Here’s how to make one. First, find an evergreen tree near your house. Clip off a few branches from the tree. Try to have as many leaves or needles on the branches as possible. Next, bring them home. What I usu…
via Anna Wise’s Blog Posts December 6, 2025
Against the Teapot Hold in Contra Dancing
The teapot hold is the most dangerous common contra dancing figure, so I’ve been avoiding it. The teapot hold, sometimes called a "courtesy turn hold,” requires one dancer to connect with their hand behind their back. When I realized I could avoid put…
via Emma Azelborn August 25, 2025