| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Scottix <scottix(at)gmail(dot)com> |
| Cc: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>, Ravi Krishna <srkrishna1(at)comcast(dot)net>, pgeu-general(at)lists(dot)postgresql(dot)org, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Inherited an 18TB DB & need to backup |
| Date: | 2020-05-15 22:07:42 |
| Message-ID: | D839F547-FF49-445A-A856-D94AB4967A19@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgeu-general pgsql-general |
> On May 15, 2020, at 12:01, Scottix <scottix(at)gmail(dot)com> wrote:
>
> Also when you get in the multi TB data storage the bill gets a little harder to digest in S3.
Indeed. Right now, just buying off of Amazon, a 12TB Seagate IronWolf drive is $0.03/GB. S3 infrequent access is $0.0125/GB/month, so the drive pays for itself (storage only) in 2.4 months. Even with an annualized failure rate of 1.4% (per Backblaze), and with the required host, rack, etc., etc., it be significantly more economical to run your own backup server. If you regularly do restores off of the backups (for example, to prime staging environments or developer systems), the outbound transfer can add up fast, too.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2020-05-15 22:25:55 | Re: Inherited an 18TB DB & need to backup |
| Previous Message | Scottix | 2020-05-15 19:01:14 | Re: Inherited an 18TB DB & need to backup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2020-05-15 22:25:55 | Re: Inherited an 18TB DB & need to backup |
| Previous Message | Andy Cooper | 2020-05-15 21:16:38 | Unexplained Access Exclusive Locks on Follower from PID7 |