Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 608319FB270 for ; Sat, 3 Feb 2007 04:19:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 59707-02 for ; Sat, 3 Feb 2007 04:18:58 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.230]) by postgresql.org (Postfix) with ESMTP id 2B5D39FB1BF for ; Sat, 3 Feb 2007 04:18:59 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id i11so1070236nzh for ; Sat, 03 Feb 2007 00:18:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Hi7nmt5C9VC9Okchz/QjZE1sCa2zSdlGLQe5AYlf1t2zK4gW2/vmRzw35Iamxk1AmO5PjvdqmNe/ox0PQ+CxWWVRKMOU2EQA19ekBHb4ayVYPEHRcXR3/gSfHKPxbe493MHs9MWvlNQhUiUCK7ACW18j+9Hn6nbaMBejmqiPuhk= Received: by 10.65.192.16 with SMTP id u16mr7551022qbp.1170490738942; Sat, 03 Feb 2007 00:18:58 -0800 (PST) Received: by 10.65.206.17 with HTTP; Sat, 3 Feb 2007 00:18:58 -0800 (PST) Message-ID: Date: Sat, 3 Feb 2007 13:18:58 +0500 From: "Shoaib Mir" To: "Joshua Kramer" Subject: Re: Backup Strategies? Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22129_2799399.1170490738905" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/42 X-Sequence-Number: 24507 ------=_Part_22129_2799399.1170490738905 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline A cron job can always do the job using pg_dump/pg_dumpall, in case you need the incremental backup you can opt for PITR WAL based archive logs... -- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 2/3/07, Joshua Kramer wrote: > > > Hello All, > > What strategies are people using for automated, script-based backup of > databases? There are a few I can think of: > > 1. Create a "db_backup" unix user and a "db_backup" pgsql user. Grant > READ access to all objects on all databases for the "db_backup" pgsql > user. Create a .pgpass file in the home directory of the "db_backup" unix > user. Backup as needed with a script run as the "db_backup" unix user. > > 2. Create a "db_backup" unix user and repeat above, except using the > "postgres" db user. > > Thanks, > -Josh > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > ------=_Part_22129_2799399.1170490738905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline A cron job can always do the job using pg_dump/pg_dumpall, in case you need the incremental backup you can opt for PITR WAL based archive logs...

--
Shoaib Mir
EnterpriseDB ( www.enterprisedb.com)

On 2/3/07, Joshua Kramer <josh@globalherald.net> wrote:

Hello All,

What strategies are people using for automated, script-based backup of
databases?  There are a few I can think of:

1. Create a "db_backup" unix user and a "db_backup" pgsql user.  Grant
READ access to all objects on all databases for the "db_backup" pgsql
user.  Create a .pgpass file in the home directory of the "db_backup" unix
user.  Backup as needed with a script run as the "db_backup" unix user.

2. Create a "db_backup" unix user and repeat above, except using the
"postgres" db user.

Thanks,
-Josh


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

------=_Part_22129_2799399.1170490738905--