SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-10-2008, 07:09 AM
| ||||
| ||||
 Backup Strategies? 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      |
|
04-10-2008, 07:09 AM
| |||
| |||
| Re: Backup Strategies? 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 > |
|
04-10-2008, 07:09 AM
| |||
| |||
| Re: Backup Strategies? After takin a swig o' Arrakan spice grog, josh@globalherald.net (Joshua Kramer) belched out: > 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. My department took the approach of having a set of "admin-specific" users, much in the spirit of 1. For backups, vacuuming, and replication, the respective clever names were dumpy, molly, and slony. (When auditors asked about the new users, there was much snickering...) We didn't create a special Unix account for it; that seemed unnecessary. -- (format nil "~S@~S" "cbbrowne" "linuxfinances.info") http://cbbrowne.com/info/rdbms.html Who wants to remember that escape-x-alt-control-left shift-b puts you into super-edit-debug-compile mode? (Discussion in comp.os.linux.misc on the intuitiveness of commands, especially Emacs.) |
|
04-10-2008, 07:09 AM
| ||||
| ||||
| Re: Backup Strategies? Thanks for the hint, Shoaib. My question - and I should have phrased this more carefully - related to the security of the various backup tactics. Is it more secure to have a "backup user" with read permissions on all databases, or is it more secure to have a dedicated Unix backup user - with the .pgpass file in the home directory and all. If someone can, by way of cracking, get in to the account of the backup Unix user, then the postgres user's database account is also surrendered. If I have a Postgres backup user (with read only permissions on all DB's), then even if someone got into the unix account of the backup user, all they could do is read DB data (versus delete or write over stuff). Essentially it's the diffrenece between being *really* secure and *really really* secure. On Sat, 3 Feb 2007, Shoaib Mir wrote: > 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 >> > ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate |
Linear Mode
