From: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com> |
---|---|
To: | "Joshua Kramer" <josh(at)globalherald(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Backup Strategies? |
Date: | 2007-02-03 08:18:58 |
Message-ID: | bf54be870702030018s74b1e916yb0787dd8f91f940d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)globalherald(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shoaib Mir | 2007-02-03 08:24:29 | Re: Terminating a query that appears to be hung |
Previous Message | Joshua Kramer | 2007-02-03 06:51:56 | Backup Strategies? |