| From: | Patrick Macdonald <patrickm(at)redhat(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Incremental backup |
| Date: | 2003-02-14 00:24:13 |
| Message-ID: | 3E4C372D.B3E90C89@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> Patrick Macdonald wrote:
>
> > Yeah, it's a different method of producing a similar outcome. However, many
> > companies do not want to be concerned with the management (and space)
> > of archived logs. Incremental backup allows them the option of performing
> > a full backup and then only backing up the modifications on a regular basis.
> > When it's time to restore, they'll restore the full backup and then the
> > proper sequence of incremental backups.
>
> Wow, I never even thought that was possible. Do other db's support that
> feature?
I know Oracle and DB2 have incremental backup in their arsenal (and iirc,
SQL Server has something called "differential backup"). Whatever the name,
it's a win at the enterprise level.
Cheers,
Patrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shahbaz Chaudhary | 2003-02-14 00:25:03 | Re: java access to the backend (non jdbc)? |
| Previous Message | Adam Haberlach | 2003-02-14 00:22:40 | Re: location of the configuration files |