From mboxrd@z Thu Jan 1 00:00:00 1970 References: <3f8aecd8ac9fdcd39dc36b5e89882c7d@orthanc.ca> <9f9c7658554a9f3fcb334aa6dbeb05ae@coraid.com> From: Anthony Sorace Content-Type: text/plain; charset=us-ascii In-Reply-To: <9f9c7658554a9f3fcb334aa6dbeb05ae@coraid.com> Message-Id: <9A9D3E68-9496-4511-91B9-DCB2A491E244@9srv.net> Date: Sat, 1 Oct 2011 04:21:01 -0400 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8E600) Subject: Re: [9fans] OT: how do 9fans backup their Mac(book)? Topicbox-Message-UUID: 2ddf2fca-ead7-11e9-9d60-3106f5b1d025 On Sep 30, 2011, at 13:59, erik quanstrom wrote: > backup: > 1. power down mac. remove hard drive. > 2. stuff drive as one gigantic file into venti. >=20 > restore: > 1. copy your backup onto drive > 2. install hard drive. power up mac. In principal, that's roughly what vbackup does, except with file systems ins= tead of whole disks and without taking things apart. I decided I didn't need= to store each version of the OS files; if you want whole images, look at vb= ackup (or, yes, time machine). I don't buy the backup/archive distinction as defined. It's totally coherent= to say "I want a backup of data set xyz", where that isn't exactly one file= system. I have backups of the data I care about, and I've judged that, for m= y usage, the moderate inconvenience and tiny risk of not having full FS back= ups is worth the trade off. (note I don't dispute that backup/archive is an important distinction, I jus= t think that draws the line in the wrong place.)=