From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] s3venti
Date: Mon, 11 Feb 2008 12:44:53 -0800 [thread overview]
Message-ID: <20080211204454.069BE5B60@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 11 Feb 2008 11:39:23 EST." <676c3c4f0802110839o1c2f6b3ft3d73eee940418be5@mail.gmail.com>
On Mon, 11 Feb 2008 11:39:23 EST "Richard Bilson" <rcbilson@gmail.com> wrote:
> > 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.
In using S3 for off-site backups I would worry about the time
to restore a failed disk (apart from the privacy issues). As
an example restoring a 100GB disk over the 'net at a constant
300KB/s of download speed can take close to 4 days. Of
course, these days many people have much more data than that.
May be there are other remote backup companies that provide a
"copy your data to disk and deliver it overnight" service for
an extra charge.
next prev parent reply other threads:[~2008-02-11 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 4:19 Richard Bilson
2008-02-11 7:11 ` Skip Tavakkolian
2008-02-11 14:49 ` erik quanstrom
2008-02-11 16:39 ` Richard Bilson
2008-02-11 20:44 ` Bakul Shah [this message]
2008-02-12 11:44 ` Alf
2008-02-12 12:43 ` erik quanstrom
2008-02-11 22:34 ` Skip Tavakkolian
2008-02-11 22:49 ` Richard Bilson
2008-02-12 9:26 ` Wilhelm B. Kloke
2008-02-12 17:45 ` Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080211204454.069BE5B60@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).