Postgres Pro
Downloads
Home   >   mailing lists

Re: Cold backup with rsync -- WAL files? - Mailing list pgsql-admin

From Payal Singh
Subject Re: Cold backup with rsync -- WAL files?
Date
Msg-id CANUg7LB6yQp4YngQ9zrPHU2OeB5T120Z_hvRoJx9RAvjHbgu8A@mail.gmail.com
Whole thread Raw
In response to Re: Cold backup with rsync -- WAL files?  (Craig James <cjames@emolecules.com>)
Responses Re: Cold backup with rsync -- WAL files?  (Craig James <cjames@emolecules.com>)
List pgsql-admin
Tree view
Not sure how/why you didn't get my reply:

If your offsite backup server has enough space to accommodate all backups that your retention period requires, backing up WAL archives is always a good idea as it could not only help you restore the standalone database, but also allow you to set up a slave if need be.

Another way to think about it would be a backup without WAL files would be ideally just a base backup, while the one with WAL files will give you point in time recovery. It all depends on what you want your backups to be used for.


Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253


On Fri, Dec 6, 2013 at 1:39 PM, Craig James <cjames@emolecules.com> wrote:
While I appreciate suggestions of other ways to do replication, does anyone have an answer to my original question?
...The procedure I'd like to implement is:
  server B is always "cold" (Postgres not running)
  while A is running, rsync A --> B
  stop Postgres on A
  rsync A --> B
  restart Postgres on A

My question is: what about the WAL files?  Do I need to rsync them from A to B too, or can/should I just clean out B's WAL directory, or something else?

Thanks,
Craig





pgsql-admin by date:

Previous
From: Craig James
Date:
Subject: Re: Cold backup with rsync -- WAL files?
Next
From: Craig James
Date:
Subject: Re: Cold backup with rsync -- WAL files?