Skip site navigation (1) Skip section navigation (2)

Re: Warm Standby - log shipping

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Mark Steben" <msteben(at)autorevenue(dot)com>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Warm Standby - log shipping
Date: 2008-12-19 17:35:50
Message-ID: 494B8716.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
>>> "Mark Steben" <msteben(at)autorevenue(dot)com> wrote: 
> What I'm hearing is that I have to perform a base backup on my master
in
> Mass. after recovery completes, send that over a secure network
> To Virginia, and lay it down there.
 
I'm not sure we're understanding each other.  I was suggesting that
you needed to make a new base backup in Mass. and send it to Virginia.
 Recovery doesn't start until you get that.  There is one way you
might avoid that, though -- if you saved a copy of the original base
backup and all WAL files since then you could start over and roll all
the way to current.
 
> Simple enough but the time to travel
> Over the network becomes an issue - 12 - 13 hours at best.
 
As already suggested, if you're not using rsync with a daemon, you
should look at that.  For us, at least, it typically cuts the copy
time by an order of magnitude.
 
If you have the room and follow the advice given in my previous post,
your warm standby should never come out of recovery mode.  You can
stop and start the server without that happening.  What I was
suggesting was that you periodically (daily?) you stop the warm
standby in Virginia, copy the data directory to another location,
restart the warm standby in recovery mode, then start up the copy of
the warm standby in recovery mode, take that out of recovery mode, and
use it for your reports.
 
-Kevin

In response to

Responses

pgsql-admin by date

Next:From: Mark StebenDate: 2008-12-19 18:09:16
Subject: Re: Warm Standby - log shipping
Previous:From: Simon RiggsDate: 2008-12-19 17:12:05
Subject: Re: Warm Standby - log shipping

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group