Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41957=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1VoxGr-0004SZ-8Y
 for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2013 15:24:49 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41957=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1VoxGq-0002C2-HS
 for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2013 15:24:48 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <scott@journyx.com>) id 1VoxGp-0002AA-3C
 for pgsql-admin@postgresql.org; Fri, 06 Dec 2013 15:24:47 +0000
Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com)
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <scott@journyx.com>) id 1VoxGe-0000vG-Cn
 for pgsql-admin@postgresql.org; Fri, 06 Dec 2013 15:24:46 +0000
Received: from localhost (localhost.localdomain [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id D25BFC423F;
 Fri,  6 Dec 2013 09:24:34 -0600 (CST)
X-Virus-Scanned: amavisd-new at zimbra.int.journyx.com
Received: from mail.int.journyx.com ([127.0.0.1])
 by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id F1CW4foNboyJ; Fri,  6 Dec 2013 09:24:28 -0600 (CST)
Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5])
 by mail.int.journyx.com (Postfix) with ESMTP id 9BF42C425F;
 Fri,  6 Dec 2013 09:24:28 -0600 (CST)
Date: Fri, 6 Dec 2013 09:24:28 -0600 (CST)
From: Scott Whitney <scott@journyx.com>
Reply-To: Scott Whitney <swhitney@journyx.com>
To: Craig James <cjames@emolecules.com>
Cc: pgsql-admin@postgresql.org
Message-ID: <23125649.944094.1386343468257.JavaMail.root@mail.int.journyx.com>
In-Reply-To: 
 <CAFwQ8rd+oDkLG4KWkux=2jwNinBnuwhY8DH3W-_58MGO1m3=Lg@mail.gmail.com>
Subject: Re: Cold backup with rsync -- WAL files?
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_Part_944093_13950612.1386343468254"
X-Originating-IP: [192.168.100.1]
X-Mailer: Zimbra 7.2.4_GA_2900 (ZimbraWebClient - GC31 (Win)/7.2.4_GA_2900)
X-Pg-Spam-Score: 0.6 (/)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

------=_Part_944093_13950612.1386343468254
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Why not use cascading replication for this? That's precisely what I'm doing. 

----- Original Message -----

> We need a "last chance" offsite backup of our backup server. Since
> the backup server isn't accessed by customers, we have the luxury of
> being able to shut it off briefly once per day. Call server "A" the
> backup, server "B" is offsite backup-of-backup: 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

------=_Part_944093_13950612.1386343468254
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>Why not use cascading replication for this? That's precisely what I'm doing.<br><br><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr"><div><div><div><div><div>We need a "last chance" offsite backup of our backup server.&nbsp; Since the backup server isn't accessed by customers, we have the luxury of being able to shut it off briefly once per day. Call server "A" the backup, server "B" is offsite backup-of-backup: The procedure I'd like to implement is:<br>
<br></div><div>&nbsp; server B is always "cold" (Postgres not running)<br></div>&nbsp; while A is running, rsync A --&gt; B<br></div>&nbsp; stop Postgres on A<br></div>&nbsp; rsync A --&gt; B<br></div>&nbsp; restart Postgres on A<br><br>
</div>My question is: what about the WAL files?&nbsp; 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?<br><div><div><div><div><div><br></div><div>Thanks,<br>Craig<br>
<br></div></div></div></div></div></div>
</blockquote><br></div></body></html>
------=_Part_944093_13950612.1386343468254--