From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E780E138CA3 for ; Sat, 9 May 2015 12:59:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 289A8E086D; Sat, 9 May 2015 12:59:52 +0000 (UTC) Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 17977E0821 for ; Sat, 9 May 2015 12:59:50 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so46117300igb.0 for ; Sat, 09 May 2015 05:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=urTwgYSgVQYnFqDrGoHuumfzcX2SY8Mk7tbVEv7+1+M=; b=hYH2D9F1Px0TSSW68tN1+pMim2u/+xNC3W8jKHgB0Gny+jdc6Po1i0LTprosIfOpNi rE0yBWiRyx0U6Bm9dC4IYDa9nDOyhgrBS4E2d/ZVYFbZJxsgA/fHJuU/HnHrEchOsJYp c4nW7WHHBX8mUHS/OndvXpA1sooqe94obFernGpn6wmdN2kHr9Pk3sV5wF88mmM97AQ0 IS0y8ntVc2CkouxGJqry7iokB68PG/TV+/daLS2u0es1ECGPGV9jVt3iJeWbczb8kfgp B8m0lXcsls2Z2a4wITxP/ylY4jQ+7jw/qHQbw8vW12iA5wx9WbFHKiGPfzPXV0QfnwIU lkaw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.42.63.80 with SMTP id b16mr2735602ici.64.1431176390414; Sat, 09 May 2015 05:59:50 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.107.48.66 with HTTP; Sat, 9 May 2015 05:59:50 -0700 (PDT) In-Reply-To: <554DE7CC.4070707@gmail.com> References: <553F474E.4040101@gmail.com> <553FA0DD.1090101@gmail.com> <20150428162448.160e1683@digimed.co.uk> <55407695.7000808@gmail.com> <20150429085217.38864030@hactar.digimed.co.uk> <5547221E.4020809@gmail.com> <20150504084626.26fbbbd8@digimed.co.uk> <55472C94.1080606@gmail.com> <20150504113149.0f61d4f9@digimed.co.uk> <55474C99.9090406@gmail.com> <20150504122636.4afc2e81@digimed.co.uk> <554DE7CC.4070707@gmail.com> Date: Sat, 9 May 2015 08:59:50 -0400 X-Google-Sender-Auth: 1rJ66OPsj52Rqi-BsV0PHYjX7Cw Message-ID: Subject: Re: [gentoo-user] Hard drive storage questions From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: f1b8d9ba-01b8-4857-b343-d52491c2c2a7 X-Archives-Hash: 09deae9a84596ef2a288a8cc36b54c5c On Sat, May 9, 2015 at 6:56 AM, Dale wrote: > > https://aws.amazon.com/s3/ > > I'm trying to figure out just how much this would cost here. o_O Just > for my pics tho. > It works out to 1-3 cents/GB/month, depending on storage tier. Glacier is cheapest and very secure (or so they claim), but you will pay more to retrieve the data if you need it. If you aren't using RAID then I probably wouldn't use glacier since it is very likely that you'll be doing retrievals on occasion. The most expensive figure costs you 10c/GB to retrieve, and should be secure (again, their claims). The in-between figure is for reduced redundancy - it also costs 10c/GB to retrieve, but is less secure. I typically use the mid-cost reduced-redundancy option, since this is intended solely as a backup. If I were archiving data and not keeping a copy locally I would not use reduced-redundancy. As a backup, it is already redundant - what are the odds of my house and the Amazon datacenter having a disaster on the same day? Otherwise, if their datacenter burns down and the data disappears, then on the next day duplicity will simply do another full backup and I'm protected again. One thing you can't cheaply do with Amazon is verify your backups. Duplicity will happily check the data files against the manifest hashes with a simple command, but it will cost you 10c/GB for whatever you verify, since it will need to be transferred out. I guess another option is to launch an EC2 instance with duplicity on it and have it do the verify. That would be an internal Amazon transfer which is both free and much faster, but it will cost you a few cents per hour for the CPU time. I also don't know if duplicity can verify a backup without the encryption keys - if it can't then you'll have to upload your keys to EC2 which means Amazon could read your backups if they wanted to. Otherwise duplicity is encrypting locally and all Amazon does is store a bunch of encrypted data and regurgitate it on demand. -- Rich