Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E20679FA307 for ; Tue, 6 Feb 2007 09:33:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 08806-01 for ; Tue, 6 Feb 2007 09:33:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by postgresql.org (Postfix) with ESMTP id 967639FA21A for ; Tue, 6 Feb 2007 09:33:35 -0400 (AST) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 48931118A2F; Tue, 6 Feb 2007 08:33:33 -0500 (EST) Date: Tue, 6 Feb 2007 08:33:33 -0500 From: Ray Stell To: Phillip Smith Cc: pgsql-admin@postgresql.org Subject: Re: Backup Strategies? Message-ID: <20070206133333.GI32722@cns.vt.edu> References: <1170494928.9214.10.camel@phillips-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1170494928.9214.10.camel@phillips-desktop> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/80 X-Sequence-Number: 24545 On Sat, Feb 03, 2007 at 08:28:48PM +1100, Phillip Smith wrote: > 1) As part of a backup script, call pg_dumpall as the postgres *nix > users and PG user, then pipe the output to a file on a remote server. might consider adding scp to the mix so that the data is not in the clear on the wire. You can use the authorized_keys feature so that passwd is not needed in the script.