pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Eduardo J. Ortega <ejortegau@cable.net.co>
To: pgsql-admin@postgresql.org
Subject: Re: Incremental Backup of a particular database
Date: Wed, 17 Jan 2007 23:09:57 -0500
Message-ID: <200701172309.59137.ejortegau@cable.net.co> (raw)
In-Reply-To: <bf54be870701170723i6465828eye3e171365a18b379@mail.gmail.com>
References: <001201c73a3e$33bbaf70$0404a8c0@central.newgen.local>
	<45AE3D9A.7010908@mailnetwork.co.uk>
	<bf54be870701170723i6465828eye3e171365a18b379@mail.gmail.com>

Not sure, but i think WAL based incremental backup is for the whole database 
cluster, and not for an specific database, so don't think this is going to 
work for you. Is yoor database too large? If not, you could stick to the old 
fashioned pg_dump output.

On Wednesday 17 January 2007 10:23, Shoaib Mir wrote:
> Yes, I guess that is true with 8.2 but with a few configurations for WAL
> copying scripts.
>
> Saw the following in documentation that specifies a good flow for doing it
> --> http://www.postgresql.org/docs/8.2/static/warm-standby.html
>
> ---------------
> Shoaib Mir
> EnterpriseDB (www.enterprisedb.com)
>
> On 1/17/07, Andy Shellam (Mailing Lists) <
>
> andy.shellam-lists@mailnetwork.co.uk> wrote:
> > Shoaib Mir wrote:
> > > Even with ver 8.1 you can use WAL archive backups (PITR) to implement
> > > an incremental backup strategy.
> >
> > Yes, true, but it's harder with 8.1 as you always have to start from a
> > base backup and roll WAL logs forward - without a custom script you
> > cannot "wait" for new WAL logs to arrive and apply them on top of a base
> > backup.
> > There is a project in PgFoundry to allow for warm-standby in the 8.0 and
> > 8.1 series, however this is reportedly built-in to 8.2 now.
> >
> > > -------------
> > > Shoaib Mir
> > > EnterpriseDB (www.enterprisedb.com <http://www.enterprisedb.com;)
> > >
> > > On 1/17/07, *Andy Shellam (Mailing Lists)*
> > > <andy.shellam-lists@mailnetwork.co.uk
> > > <mailto:andy.shellam-lists@mailnetwork.co.uk>> wrote:
> > >
> > >     I believe the option for a "warm standby" (which sounds like it is
> > >     what
> > >     you need) was made available in 8.2.0.
> > >     You'd have to look at the manual though, I haven't had time to
> > >     investigate, and I'm not sure whether it's cluster-wide, or
> > >     database-specific.
> > >
> > >     Yogvinder Singh wrote:
> > >     > Hi Ppl,
> > >     >
> > >     > I have Two PostgreSQL Database Servers. The situation is like
> >
> > this:-
> >
> > >     > 1) On first database server ball the operations (i.e live
> > >
> > >     server) will
> > >
> > >     > be done. This server may contain n number of databases.
> > >     >
> > >     > 2) On the second database server, i want to keep one particular
> > >     > database (from the first database server  ) and keep it updated
> > >
> > >     to the
> > >
> > >     > latest from the First Database Server. I just want to be able to
> > >
> > >     take
> > >
> > >     > some sort of incremental backup from the first server and restore
> >
> > it
> >
> > >     > to the second server.
> > >     >
> > >     > Is this situation feasible. How can i take an incremental backup
> > >
> > >     of a
> > >
> > >     > particular database out of many databases? On which version this
> >
> > is
> >
> > >     > supported? IF not supported, is there any alternative way to
> >
> > handle
> >
> > >     > this situatio.
> > >     >
> > >     > Regards,
> > >     > Yogvinder Singh,
> > >     > Disclaimer :- This e-mail message
> > >     > including any attachment may contain confidential, proprietary or
> > >     > legally privileged information. It should not be used by who is
> >
> > not
> >
> > >     > the original intended recipient. If you have erroneously
> > >
> > >     received this
> > >
> > >     > message, you are notified that you are strictly prohibited from
> > >
> > >     using,
> > >
> > >     > copying, altering or disclosing the content of this message.
> >
> > Please
> >
> > >     > delete it immediately and notify the sender. Newgen Software
> > >     > Technologies Ltd and / or its subsidiary Companies accept no
> > >     > responsibility for loss or damage arising from the use of the
> > >     > information transmitted by this email including damage from
> > >
> > >     virus and
> > >
> > >     > further acknowledges that any views expressed in this message are
> > >     > those of the individual sender and no binding nature of the
> >
> > message
> >
> > >     > shall be implied or assumed unless the sender does so expressly
> > >
> > >     with
> > >
> > >     > due authority of Newgen Software Technologies Ltd and / or its
> > >     > subsidiary Companies, as applicable.
> > >
> > >     ---------------------------(end of
> > >     broadcast)---------------------------
> > >     TIP 3: Have you checked our extensive FAQ?
> > >
> > >                    http://www.postgresql.org/docs/faq
> > >
> > >
> > > !DSPAM:37,45ae3b61137103926781350!

-- 
Eduardo J. Ortega - Linux user #222873 
"No fake - I'm a big fan of konqueror, and I use it for everything." -- Linus 
Torvalds



view thread (15+ messages)  latest in thread

Message-ID: <200701172309.59137.ejortegau@cable.net.co>
Permalink:  ../200701172309.59137.ejortegau@cable.net.co/
Also on:    postgresql.org/message-id/200701172309.59137.ejortegau@cable.net.co

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: ejortegau@cable.net.co
  Subject: Re: Incremental Backup of a particular database
  In-Reply-To: <200701172309.59137.ejortegau@cable.net.co>
  References: <001201c73a3e$33bbaf70$0404a8c0@central.newgen.local> <45AE3D9A.7010908@mailnetwork.co.uk> <bf54be870701170723i6465828eye3e171365a18b379@mail.gmail.com> <200701172309.59137.ejortegau@cable.net.co>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox