From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Brian Modra <epailty(at)googlemail(dot)com> |
Cc: | Farhan Malik <malikpiano(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Out of space making backup |
Date: | 2009-12-26 02:29:16 |
Message-ID: | 4B3574FC.20009@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 26/12/2009 12:44 AM, Brian Modra wrote:
> use select pg_start_backup('some-name') (in psql logged in a postres)
> then start a tar of /var/lib/pgsql/data/, to stdout and pipe this to
> tar on another server using ssh
This won't work on a Windows machine. Windows does not permit files that
are open for write by one process to be opened by another, unless the
first process makes special efforts to permit it.
In general, people get around this by using the Volume Shadow Copy
Service (VSS) via dedicated backup software. This takes a consistent
snapshot of the file system and permits the backup software to access
that snapshot.
If you were going to take filesystem-level backups on Windows, that'd be
how you'd want to do it - have a pre hook in your backup software that
called pg_start_backup() and a post hook that called pg_stop_backup(),
letting the backup software handle the snapshot and filesystem copy.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Randal L. Schwartz | 2009-12-26 03:28:49 | Re: Clarification regarding array columns usage? |
Previous Message | Adrian Klaver | 2009-12-25 20:13:04 | Re: Updating from 8.2 to 8.4 |