Skip to main content

Fixing BackInTime Snapshot Failures

Although it's really simple to write your own rsync script to do backups on GNU/Linux, I'm a big fan of BackInTime because it's a more sophisticated, snapshot-oriented backup solution (very similar to Apple's Time Machine) as opposed to the blind copy and sync that you'd typically wind up with using a one-line rsync script.

The issue is that even when running BackInTime as root there are some directories, symlinks, etc. that it can't copy or certain operations it can't perform, so you wind up with failed snapshot errors. In the past I never really dug into them and just went back to using an rsync script to sync to my Amahi server, but today I decided to spend a bit of time working through the errors since they were exacerbated a bit due to my home directory being encrypted on my new System76 Lemur UltraThin.

What makes this process easy is that BackInTime keeps excellent logs of where it's failing, and as opposed to taking the time to investigate why each of these operations was failing, I just added a few patterns and directories to my exclude list and my snapshots are succeeding now.

The specifics in your situation may vary, but in my case I added the following to be excluded:
  • *gvfs*
  • [a few symlinks that pointed to directories in my home directory itself]
  • /home/mwoodward/.config/chromium
  • /home/.ecryptfs/mwoodward/.Private
  • /home/mwoodward/.Private
  • /home/mwoodward/.gconf
  • /home/mwoodward/.pulse
With those in the exclude list the snapshots are clean and I'm happily backing things up with BackInTime again. What I need to do next is verify that these exclusions aren't causing any issues, but since all I really need is the bulk of the files in my home directory to be backed up based on the bit of poking around I did it seems to be working fine.

Comments

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…