Comments on: Time Machine – Offsite Solutions http://www.nickstarr.com/2006/08/17/time-machine-offsite-solutions/ Mon, 15 Mar 2010 00:08:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Peter N Lewis http://www.nickstarr.com/2006/08/17/time-machine-offsite-solutions/comment-page-1/#comment-49768 Peter N Lewis Fri, 18 Aug 2006 11:35:06 +0000 http://www.nickstarr.com/2006/08/17/time-machine-offsite-solutions/#comment-49768 The next version of <a href="http://www.interarchy.com" rel="nofollow">Interarchy</a> (8.2) which is due for release in a few weeks will have a new feature that allows transparent encoding/decoding of files using one of our encoders or one you write yourself. One of the encoders we'll have is a Backup encoder that flattens all the meta data (by which, I mean all, including ACLs, BSD flags, HFS attributes, etc) into a flat file with a documented format. While slightly tricky to set up (you need to configure per-host preferences since you probably do not want *all* your files encoded, just the ones going to your backup site, you'll be able to set it up so that any folder you choose (eg, your home folder, or your Documents folder) can be mirrored to Amazon S3 (or anywhere with any protocol Interarchy supports) and transparently Backup-encoded. Of course, a true backup solution has much more than just this, it has versioning and snap shots and bootable disks and such, but as a secondary backup system or as an emergency backup system, or as your first backup system if you have no other, it should certainly be useful. I'll have more details on our <a href="http://blog.stairways.com/" rel="nofollow">blog</a> about exactly how to do it after we release Interarchy 8.2 . The next version of Interarchy (8.2) which is due for release in a few weeks will have a new feature that allows transparent encoding/decoding of files using one of our encoders or one you write yourself. One of the encoders we’ll have is a Backup encoder that flattens all the meta data (by which, I mean all, including ACLs, BSD flags, HFS attributes, etc) into a flat file with a documented format.

While slightly tricky to set up (you need to configure per-host preferences since you probably do not want *all* your files encoded, just the ones going to your backup site, you’ll be able to set it up so that any folder you choose (eg, your home folder, or your Documents folder) can be mirrored to Amazon S3 (or anywhere with any protocol Interarchy supports) and transparently Backup-encoded.

Of course, a true backup solution has much more than just this, it has versioning and snap shots and bootable disks and such, but as a secondary backup system or as an emergency backup system, or as your first backup system if you have no other, it should certainly be useful.

I’ll have more details on our blog about exactly how to do it after we release Interarchy 8.2 .

]]>