From: | Martin Bruset Solberg <martin(dot)bruset(dot)solberg(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | PITR compatible backup with exclusion |
Date: | 2015-01-26 12:17:07 |
Message-ID: | CA+Cf-b8BBFPq5HLa5TZwHgpn0gpWNDGTwE24ydvOn3QhdrLRPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I am faced with a scenario of backing up a database with one large
(partitioned) table, and several smaller tables. The large table is so big
that backing it up is proving problematic both in terms of storage and time
spent backing up and restoring. The backup of the table itself is also
reduntant, as the table data can be recreated by importing from the source
files. This data is not mission critical for the application, so a speedy
recovery is not urgent.
The data from the smaller tables, however, is critical. The combined size
of the rest of the database is not a problem neither in terms of storage or
backup/restore speed, so a logical backup excluding the large table/schema
works fine. But logical backup is not sufficiant, as I need to be able to
do PITR in case of disaster.
So my question is, what are my options when I want to make a PITR
compatible backup, and need to exclude a table/schema/tablespace of the
database? Any suggestions welcome...
Martin Bruset Solberg
From | Date | Subject | |
---|---|---|---|
Next Message | Luc DALLEMANE | 2015-01-26 16:38:00 | LDAP authentication problem. |
Previous Message | Jan Šejc | 2015-01-25 13:39:12 | Slony-I creation scripts not available; only joining possible' Windows server |