{"id":2788,"date":"2009-05-12T08:59:35","date_gmt":"2009-05-12T15:59:35","guid":{"rendered":"http:\/\/redmonk.com\/sogrady\/?p=2788"},"modified":"2009-05-12T08:59:35","modified_gmt":"2009-05-12T15:59:35","slug":"my-backup","status":"publish","type":"post","link":"https:\/\/redmonk.com\/sogrady\/2009\/05\/12\/my-backup\/","title":{"rendered":"My Backup: Dropbox, JungleDisk, S3, and a Desperate Need for Deduping"},"content":{"rendered":"

When it comes to backing up my music, I have four problems. Apart from the backup, I mean. <\/p>\n

    \n
  1. My music acquisition is done on a Linux laptop (both Amazon and the eMusic store provide Linux clients)<\/li>\n
  2. My Linux laptop’s harddrive is only 128 GB, much of which is devoted to virtual images, ergo space for music is tight<\/li>\n
  3. My primary music library is housed on a Mac (so as to be portable to my iPhone)<\/li>\n
  4. My music library (~80 GB) is too large to be entirely synced with Dropbox (50 GB max)<\/li>\n<\/ol>\n

    In other words, I currently download to one machine – an Ubuntu equipped X301 – which has only enough space to contain a subset of the master library. As for the master library, it’s attached to a Mac Mini running OS X, which in turn needs to be regularly updated with the newly acquired tracks from the Ubuntu machine. <\/p>\n

    Got all that? <\/p>\n

    Besides migrating newly acquired content to the master library, one of the requirements of my backup process is to push the content to the cloud. As I noted in 2007, my music may just be my most valuable material possession<\/a>, and it’s certainly the least replaceable, so having an offsite copy is critical to me. Just as it will be to a horde of consumers in the years ahead, but that’s a different matter entirely. <\/p>\n

    So here’s my solution, warts and all – and yes, I’ll get to those. <\/p>\n

    Tools<\/h2>\n