From: | "Ravi Krishna" <srkrishna1(at)comcast(dot)net> |
---|---|
To: | |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, pgeu-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Inherited an 18TB DB & need to backup |
Date: | 2020-05-15 17:51:37 |
Message-ID: | em71122277-5d45-40e4-bfbe-b234caf0fdbb@ip-192-168-0-67.ec2.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgeu-general pgsql-general |
>
>Why should the backup land in S3, and not local somewhere?
>Any good reason why one should pay for the additional storage and
>transfer costs?
>
Good question. The key point in my statement was "db of this size".
The problem with local backup is that space is not infinite. If your
business requires you to
store backups for say 7 years, storing it locally will be a problem. In
one large financial
company I use to work, full backup was used to store old data.
(except last 30 days where WAL logs were used for a real PIT). We use
to store full backups
for about 60 days and then send older backup to an off site storage.
Nothing is free.
I remember a case where we were requested by business to restore a db of
a given date two yrs
prior as they had to look at old data. It took us close to 96 hrs to
give the users the required database.
S3 storage is ridiculously cheap. Off site storage companies like Iron
Mountain should find their client base
ditching them big time.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2020-05-15 18:49:15 | Re: Inherited an 18TB DB & need to backup |
Previous Message | Andreas 'ads' Scherbaum | 2020-05-15 17:33:27 | Re: Inherited an 18TB DB & need to backup |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-05-15 17:55:25 | Re: Bug on version 12 ? |
Previous Message | Andreas 'ads' Scherbaum | 2020-05-15 17:33:27 | Re: Inherited an 18TB DB & need to backup |