::  Posts  ::  RSS  ::  ◂◂RSS  ::  Contact

Backup Strategy

January 22nd, 2019
tech  [html]
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

Recent posts on blogs I like:

The Private Sector’s Role in Transit Innovation

The United States has long had private success and public failure – not just the sense of private affluence and public squalor, in which household income is high but the state of public services lags, but also in that the private sector is more productive…

via Pedestrian Observations June 17, 2019

Unintended pregnancy in folk songs

I’ve been listening to a lot of the Watersons and Waterson:Carthy this week. It’s reminded me how absolutely full British folk music is of songs about unintended pregnancy. Most commonly the result is unhappy motherhood: “But if I had kent that I now ken …

via The whole sky June 1, 2019

Programmer migration patterns

I made a little flow chart of mainstream programming languages and how programmers seem to move from one to another. There's a more common kind of chart, which shows how the languages themselves evolved. I didn't want to show the point of view of …

via apenwarr March 18, 2019

more     (via openring)

More Posts:


  ::  Posts  ::  RSS  ::  ◂◂RSS  ::  Contact