From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | senthilnathan <senthilnathan(dot)t(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Backup's from standby |
Date: | 2011-08-11 16:30:28 |
Message-ID: | CA+TgmoZ6Hxdo_euAXwjWr_8tEZ+7+88dPjQwtyGzH40Ezc3Cjw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 11, 2011 at 1:02 AM, senthilnathan
<senthilnathan(dot)t(at)gmail(dot)com> wrote:
> What is the basic reason for restricting backup at standby
> server(pg_start_backup)?
It performs a checkpoint.
> We are doing the following steps to take backup from standby which(backups)
> might be used for standalone startups.
>
> 1.Create file system snapshot(LVM)
> 2.take the back up of data directory including wal files
> 3.Drop the file system snapshot
>
> Will there be(foresee) any issues while using these backups?
Assuming that step #2 is backing up an instantaneous snapshot, rather
than the live data directory, I think that will work. Upon starting
up the server, it will enter recovery, but the WAL present in the data
directory at the time of the snapshot should be sufficient to reach
the minimum recovery point.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-08-11 17:50:02 | Re: small issue with host names in hba |
Previous Message | Joshua D. Drake | 2011-08-11 16:26:18 | Final 48 for PgWest CFP |