Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 1E7949FB25F for ; Tue, 6 Feb 2007 17:30:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 23236-03 for ; Tue, 6 Feb 2007 17:29:59 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from weatherbeeta.com.au (218-214-212-153.people.net.au [218.214.212.153]) by postgresql.org (Postfix) with SMTP id 292EB9FB251 for ; Tue, 6 Feb 2007 17:29:57 -0400 (AST) Received: (qmail 15373 invoked from network); 6 Feb 2007 21:29:55 -0000 X-NetworkBox-HamSign: 0101;OUT;wbeetaau1;83427e6cb553e0480297ca027b359849; Received: from mail.weatherbeeta.com.au (10.10.0.2) by network-box.weatherbeeta.com.au with SMTP; 6 Feb 2007 21:29:55 -0000 Received: (qmail 2954 invoked by uid 1166); 7 Feb 2007 08:29:54 +1100 Received: from 172.20.0.155 by mail.weatherbeeta.com.au (envelope-from , uid 1165) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.6/2315. perlscan: 1.25-st-qms. Clear:RC:1(172.20.0.155):. Processed in 0.215056 secs); 06 Feb 2007 21:29:54 -0000 X-Antivirus-mail.weatherbeeta.com.au-Mail-From: phillip.smith@weatherbeeta.com.au via mail.weatherbeeta.com.au X-Antivirus-mail.weatherbeeta.com.au: 1.25-st-qms (Clear:RC:1(172.20.0.155):. Processed in 0.215056 secs Process 2948) Received: from it-phil.weatherbeeta.com.au (HELO wbaus090) (172.20.0.155) by mail.weatherbeeta.com.au with SMTP; 7 Feb 2007 08:29:53 +1100 From: "Phillip Smith" To: "'Ray Stell'" Cc: Subject: Re: Backup Strategies? Date: Wed, 7 Feb 2007 08:29:52 +1100 Organization: Weatherbeeta Pty Ptd Message-ID: <002601c74a35$f052d170$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <20070206133333.GI32722@cns.vt.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Importance: Normal X-Scanned-By-wbeetaau1: Virus scan performed by network-box X-Scanned-By-wbeetaau1: Scanner file id is wbeetaau1-1170797395.98-15368-000 X-Scanned-By-wbeetaau1: No known viruses found in message (received+scanned in 0.02/0.07 secs) X-Scanned-By-wbeetaau1: Spam-Check-Result: No, hits=0 required=7 tests= autolearn=no version=2.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/82 X-Sequence-Number: 24547 I actually dump to a local file, then include that in a TAR GZ file, so it's not actually in plain text on the network, although not truly encrypted either... Cheers, -p -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Ray Stell Sent: Wednesday, 7 February 2007 00:34 To: Phillip Smith Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Backup Strategies? 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. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly *******************Confidentiality and Privilege Notice******************* The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments