From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <676c3c4f0802110839o1c2f6b3ft3d73eee940418be5@mail.gmail.com>
Date: Mon, 11 Feb 2008 11:39:23 -0500
From: "Richard Bilson" <rcbilson@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] s3venti
In-Reply-To: <95720658912c7b8567ed713b0ac7459f@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <676c3c4f0802102019o468a6191uf5b2872d89c57481@mail.gmail.com>
	<95720658912c7b8567ed713b0ac7459f@quanstro.net>
Topicbox-Message-UUID: 501a1266-ead3-11e9-9d60-3106f5b1d025

> what usage senerio do you have in mind for venti/s3?

I wanted "set it and forget it" off-site backups, at a reasonable cost
and without significant capital outlays or maintenance. I.e., mirror
an existing venti with a cron job, or use it as a target for vbackup.
As you point out, whether the cost of S3 is reasonable depends on how
much you have to store, and how much it's worth to you to store it. I
don't intend to use it for my mp3s, for instance.

An additional advantage of s3venti is that multiple s3venti servers
can use the same S3 bucket and exploit redundancies in the data across
servers. That's not of particular use to me right now, but it seemed
interesting.