>
> We're not doing this long-term, in order to have a backup server we can
> fail-over to, but rather as a one-off low impact move of our database.
> Consequently, instead of using pg_start_backup and pg_stop_backup, and
> keeping all WAL, we're stopping the database, rsync of everything, and
> st
On Tue, Nov 1, 2011 at 11:08 AM, Alan Hodgson wrote:
> On October 31, 2011 03:01:19 PM Stephen Denne wrote:
>> I'm wondering whether it's worth doing anyway, simply to check that it
>> doesn't do something completely unexpected, which would presumably alert
>> us to something we hadn't considered.
On October 31, 2011 03:01:19 PM Stephen Denne wrote:
> I'm wondering whether it's worth doing anyway, simply to check that it
> doesn't do something completely unexpected, which would presumably alert
> us to something we hadn't considered.
>
Testing is always worthwhile, if only to ensure that P
Thanks for sharing your experience and thoughts Venkat,
Venkat Balaji said:
> We are performing backups to our production server exactly the same way. We
> have been through some problems while restoring and bringing up the database.
> If you are planning to take initial complete rsync with sub
>
> "Another option is to use rsync to perform a file system backup. This is
> done by first running rsync while the database server is running, then
> shutting down the database server just long enough to do a second rsync. The
> second rsync will be much quicker than the first, because it has rel
On Thu, Oct 27, 2011 at 7:37 PM, Stephen Denne
wrote:
> We're intending to move a 470GB PostgreSQL 8.3.13 database using the
> following technique from
> http://www.postgresql.org/docs/8.3/interactive/backup-file.html
>
> "Another option is to use rsync to perform a file system backup. This is d
We're intending to move a 470GB PostgreSQL 8.3.13 database using the following
technique from http://www.postgresql.org/docs/8.3/interactive/backup-file.html
"Another option is to use rsync to perform a file system backup. This is done
by first running rsync while the database server is running