Thank goodness for backups

After updating the darwinports subversion port to 1.0.3 this morning, I noticed several problems.

Initially I thought it was something strange with the update so I downgraded to the 1.0.2 version, but further investigation pointed to a problem with my local repository. It seems that at some point the power outages this weekend caused the database to become corrupted (or the drive that the repository is on is almost dead, Jared said that he saw some console spew about IO errors, but I haven't seen anything since then - I'll have to monitor it closely). I've restored a backup from just before that and things seem to be ok again. (Fortunately, I had local copies of all of the modifications I've made since them, so they were easy to re-commit to the repository and get things up-to-date again).

I also found a patch that should let svnlook diff work correctly on Mac OS X again (yay!).

Lesson: Paranoid backup solutions are a really good idea. This is the second time it's saved my work repository.

| 3 Comments

3 Comments

"...Paranoid backup solutions..."

Examples? Details? What Media Rotation? FULL, DIFFERENTIAL, INCREMENTAL? FULL+DIFF? FULL+INCRE? Tape Involved? ANSWERS!!! ;)

I'm mainly concerned with keeping my subversion repository (work stuff) safe.

So, I do a nightly dump (and keep ~ a week of these) to a backup directory that gets both copied to my other machine (with a mirrored raid setup) and gets copied to my iDisk.

I have a few other critical files backed up that way too. Everything else I either don't really care if I loose or I have some way of restoring it (CD-R, DVD-R, whatever).

Tape is too expensive.

Is that enough data for you?

Yes, that satisfies my curiosity ... for now ;)

Everyone seems to have a unique backup strategy so I am always interested to find out who does what.

Powered by Movable Type 4.34-en
Creative Commons License
This blog is licensed under a Creative Commons License.