From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Erik Jones <erik(at)myemma(dot)com>, Brian Wipf <brian(at)clickspace(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: WARNINGs after starting backup server created with PITR |
Date: | 2008-01-19 08:17:21 |
Message-ID: | 200801190317.21810.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday 18 January 2008 18:04, Erik Jones wrote:
> For our primary, er, main, onsite standby server that's also what we
> do. But, this was a co-location to co-location transfer so there was
> no NFS mount, it was a direct rsync to the server at the other co-
> location. For WAL files, I've already decided to write a WALShipper
> utility that will handle shipping WALs to multiple standbys with
> verfication, but for the base backup, this is distressing. We do
> have the option to do the base backup to a portable USB drive and
> then carry it to the second co-lo for now. But, pretty soon we're
> going to be surpassing the available limits in portably drive
> capacity unless we invest in tape drives.
>
Are you guys running ZFS yet? If so it's snapshot / cloning capabilities might
be the way to go.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-01-19 08:26:37 | Re: WARNINGs after starting backup server created with PITR |
Previous Message | Tom Lane | 2008-01-19 00:58:19 | Re: WARNINGs after starting backup server created with PITR |