philippe::niquille | irregular niche market thoughts

Followup: Amazon S3 tripple encrypted true Rsync backup

Jun 18th 2008
4 Comments
respond
trackback

Since I had problems with rsync 2.6.3 not properly excluding directories with whitespaces I figured out a dirty workaround. In order to really simplify the process of selecting the folders which should be rsynced I created a directory only containing symbolic links. In this directory I issued the ln -s <backup_this_directory> <my_link_name> command. Important: creating an Alias in Finder and copying that one to the folder does not work. I then added the -h option to tar and the -L to rsync to instruct them to follow symbolic links and not just copy them. The neat thing about this setup is that you can point a link which contains not whitespaces (such as My_directory) to a folder containing whitespaces (such as My Directory).

See the following screenshot for a detailed folder views.

Get v0.1.1 here.

I know this is all kind of dirty, but it does its job. As improvement I am waiting for an OS X version of rsyncrypto which should be more efficient in encryption than murk. I’ll keep you posted.

4 Comments

  1. Basti

    Just curious,

    why not use JungleDisk directly for backups to Amazon S3?
    So far I am rather satisfied with the backup procedures included in JungleDisk (2.0beta4 that is). And an 256bit AES encryption seems enough for my purposes and in case of a complete computer failure JungleDisk is available for all platforms.

    Greetz

  2. Basti, I assume you are using JungleDisk Plus then? The thing is that I was looking for a block level backup solution and since I was already familiar with rsync..

    Thanks for the input though!

  3. Basti

    Actually I do not use JungleDisk Plus as then I would have to use US-Servers, and for some reasons I just prefer European ones ;-)

    Thus I do not have a block level backup solution, but which currently is sufficient for my needs as the files I usually backup do not exceed 5MB. So not having a block level but only file level based solution is ‘acceptable’.

    Thanks to your article, I might consider starting a little command-line action and create a block level solution on European servers for myself ;-)

    Thanks and all the best

Leave a Reply