From: | Jonathan Bartlett <johnnyb(at)eskimo(dot)com> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: reliable backup techniques |
Date: | 2003-02-19 17:34:15 |
Message-ID: | Pine.GSU.4.44.0302190932150.20576-100000@eskimo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Linux, you can use the Linux volume manager, and create a temporary
snapshot and tar that up. If you have to go back to it, the database will
have to recover on startup, just as if the machine had crashed at that
point. That's much better than a regular tar, in which the database would
be likely unrecoverable.
Jon
On Wed, 19 Feb 2003, Ed L. wrote:
>
> I'd like to get some opinions on the best techniques for getting
> reliably consistent backups. My current understanding is that the
> only reliable way to get a consistent backup of a running system is
> through pg_dump or pg_dumpall. More specifically, it is my
> understanding that file backups (tar, etc) do not guarantee
> consistency due to the potential lag in cache writes to disk from
> running transactions.
>
> Is my understanding correct? Are there other ways of getting
> consistent backups of a live system?
>
> Thanks,
> Ed
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Childs | 2003-02-19 17:39:23 | Re: Table Partitioning in Postgres: |
Previous Message | Jonathan Bartlett | 2003-02-19 17:31:02 | Re: Table Partitioning in Postgres: |