pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedBackup
52+ messages / 34 participants
[nested] [flat]
* Backup
@ 2004-07-23 12:24 Eduardo S. Fontanetti <dufuzzy@yahoo.com.br>
2004-07-24 03:23 ` Re: Backup mike g <mike@thegodshalls.com>
0 siblings, 1 reply; 52+ messages in thread
From: Eduardo S. Fontanetti @ 2004-07-23 12:24 UTC (permalink / raw)
To: pgsql-admin
I have a question.
I am getting trouble to dump my database with LO
(Large Object), but exactly at restoring.
Then I ask: If I just copy the data directory from
pgsql directory, I can restore the databases just
copying this directory back from a backup?
Thanks
Eduardo
_______________________________________________________
Yahoo! Mail agora com 100MB, anti-spam e antivírus grátis!
http://br.info.mail.yahoo.com/
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2004-07-23 12:24 Backup Eduardo S. Fontanetti <dufuzzy@yahoo.com.br>
@ 2004-07-24 03:23 ` mike g <mike@thegodshalls.com>
0 siblings, 0 replies; 52+ messages in thread
From: mike g @ 2004-07-24 03:23 UTC (permalink / raw)
To: Eduardo S. Fontanetti <dufuzzy@yahoo.com.br>; +Cc: pgsql-admin
If you stop the postmaster service before copying the database directory
yes.
See http://www.postgresql.org/docs/7.4/static/backup-file.html
Mike
On Fri, 2004-07-23 at 07:24, Eduardo S. Fontanetti wrote:
> I have a question.
>
> I am getting trouble to dump my database with LO
> (Large Object), but exactly at restoring.
>
> Then I ask: If I just copy the data directory from
> pgsql directory, I can restore the databases just
> copying this directory back from a backup?
>
> Thanks
>
> Eduardo
>
>
>
>
>
> _______________________________________________________
> Yahoo! Mail agora com 100MB, anti-spam e antivírus grátis!
> http://br.info.mail.yahoo.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
^ permalink raw reply [nested|flat] 52+ messages in thread
* backup
@ 2005-01-05 05:45 Jimmy P Mani <jimmymani@gmail.com>
2005-01-08 22:20 ` Re: backup Jyry Kuukkanen <jyry@neutech.fi>
2005-01-08 22:22 ` Re: backup Michael Fuhr <mike@fuhr.org>
0 siblings, 2 replies; 52+ messages in thread
From: Jimmy P Mani @ 2005-01-05 05:45 UTC (permalink / raw)
To: pgsql-admin
hi
i have a backup of pgsql in .tar format
how can i make the database unzipped from that
jim
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2005-01-05 05:45 backup Jimmy P Mani <jimmymani@gmail.com>
@ 2005-01-08 22:20 ` Jyry Kuukkanen <jyry@neutech.fi>
1 sibling, 0 replies; 52+ messages in thread
From: Jyry Kuukkanen @ 2005-01-08 22:20 UTC (permalink / raw)
To: Jimmy P Mani <jimmymani@gmail.com>; +Cc: pgsql-admin
On Tue, 4 Jan 2005, Jimmy P Mani wrote:
> hi
> i have a backup of pgsql in .tar format
> how can i make the database unzipped from that
Hello
It seems you use MS-Win based on "unzipped" word, hence I guess you should
be able to unpack it using WinZip. In Linux/Un*x world, the command line
option is to type: tar xfv your.tar
--
--Jyry
C|:-( C|:-/ C|========8-O C|8-/ C|:-(
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2005-01-05 05:45 backup Jimmy P Mani <jimmymani@gmail.com>
@ 2005-01-08 22:22 ` Michael Fuhr <mike@fuhr.org>
1 sibling, 0 replies; 52+ messages in thread
From: Michael Fuhr @ 2005-01-08 22:22 UTC (permalink / raw)
To: Jimmy P Mani <jimmymani@gmail.com>; +Cc: pgsql-admin
On Tue, Jan 04, 2005 at 09:45:35PM -0800, Jimmy P Mani wrote:
> i have a backup of pgsql in .tar format
> how can i make the database unzipped from that
Determine how the tarball was created and use the appropriate restore
method. See the "Backup and Restore" chapter in the PostgreSQL
documentation for details.
If the tarball contains toc.dat, other .dat files, and restore.sql,
then the backup was created with pg_dump and you can use pg_restore
to restore it. See the documentation for pg_restore.
If the tarball contains files like pgsql/base/25819/17187 then it's
a file system level backup and you can restore it as you would any
other directory structure. Read carefully the "File system level
backup" section of the documentation before doing anything. Make
sure the postmaster is shut down when you do the restore.
If you need more information then please be more specific about
what concerns or problems you're having.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
^ permalink raw reply [nested|flat] 52+ messages in thread
* Backup
@ 2005-03-23 20:41 Joseph M. Day <jday@gisolutions.us>
2005-03-23 21:13 ` Re: Backup Joshua D. Drake <jd@commandprompt.com>
2005-03-23 22:37 ` Re: Backup Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 52+ messages in thread
From: Joseph M. Day @ 2005-03-23 20:41 UTC (permalink / raw)
To: pgsql-admin
I am trying to convert a MSSQL DB thats roughly 45GB, to Postgres. I am
trying to find the equivalent of Full / Incremental / Differential
backups. It looks like pg_dump is the equivalent of a full backup, but
how do I keep the equivalent of a Incremental, or Differential backup.
To keep the same functionality, I will need a full backup once a week,
and a differential once a day.
Thanks,
Joe,
--------------------------------------------
Joseph M. Day
Global Innovative Solutions
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2005-03-23 20:41 Backup Joseph M. Day <jday@gisolutions.us>
@ 2005-03-23 21:13 ` Joshua D. Drake <jd@commandprompt.com>
1 sibling, 0 replies; 52+ messages in thread
From: Joshua D. Drake @ 2005-03-23 21:13 UTC (permalink / raw)
To: Joseph M. Day <jday@gisolutions.us>; +Cc: pgsql-admin
Joseph M. Day wrote:
> I am trying to convert a MSSQL DB thats roughly 45GB, to Postgres. I
> am trying to find the equivalent of Full / Incremental / Differential
> backups. It looks like pg_dump is the equivalent of a full backup, but
> how do I keep the equivalent of a Incremental, or Differential backup.
>
> To keep the same functionality, I will need a full backup once a week,
> and a differential once a day.
If you are using >8.0 You could use the PITR functionality.
Sincerely,
Joshua D. Drake
>
> Thanks,
>
> Joe,
>
>
> --------------------------------------------
> Joseph M. Day
> Global Innovative Solutions
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Attachments:
jd.vcf (text/x-vcard, 283B) download
begin:vcard
fn:Joshua Drake
n:Drake;Joshua
org:Command Prompt, Inc.
adr:;;PO Box 215 ;Cascade Locks;OR;97014;US
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
x-mozilla-html:FALSE
url:http://www.commandprompt.com
version:2.1
end:vcard
* Re: Backup
2005-03-23 20:41 Backup Joseph M. Day <jday@gisolutions.us>
@ 2005-03-23 22:37 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 52+ messages in thread
From: Tom Lane @ 2005-03-23 22:37 UTC (permalink / raw)
To: Joseph M. Day <jday@gisolutions.us>; +Cc: pgsql-admin
"Joseph M. Day" <jday@gisolutions.us> writes:
> It looks like pg_dump is the equivalent of a full backup, but
> how do I keep the equivalent of a Incremental, or Differential backup.
The only built-in mechanism for incremental backups at the moment is
archiving WAL logs via PITR. See
http://www.postgresql.org/docs/8.0/static/backup-online.html
> To keep the same functionality, I will need a full backup once a week,
> and a differential once a day.
You might consider rsync'ing the database, though I'm not sure what sort
of performance that will give.
regards, tom lane
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
@ 2005-03-23 21:01 Joseph M. Day <jday@gisolutions.us>
2005-03-23 21:20 ` Re: Backup Jay A. Kreibich <jak@uiuc.edu>
0 siblings, 1 reply; 52+ messages in thread
From: Joseph M. Day @ 2005-03-23 21:01 UTC (permalink / raw)
To: 'Naomi Walker' <nwalke@eldocomp.com>; +Cc: pgsql-admin
Joseph M. Day wrote:
>> I am trying to convert a MSSQL DB thats roughly 45GB, to Postgres. I
>> am
>> trying to find the equivalent of Full / Incremental / Differential
>> backups. It looks like pg_dump is the equivalent of a full backup,
but
>> how do I keep the equivalent of a Incremental, or Differential
backup.
>>
>> To keep the same functionality, I will need a full backup once a
week,
>> and a differential once a day.
>>
>At this time, there is nothing less than full backups.
--
Thanks Naomi.
Is there anybody using this for large DB's? Anything larger than a
couple hundred GB, it would be impractical to make full backups
everyday. Anyone out there using this for large DB's, if so I'd love to
hear how they are dealing with backups.
Joe,
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2005-03-23 21:01 Re: Backup Joseph M. Day <jday@gisolutions.us>
@ 2005-03-23 21:20 ` Jay A. Kreibich <jak@uiuc.edu>
0 siblings, 0 replies; 52+ messages in thread
From: Jay A. Kreibich @ 2005-03-23 21:20 UTC (permalink / raw)
To: Joseph M. Day <jday@gisolutions.us>; +Cc: 'Naomi Walker' <nwalke@eldocomp.com>; pgsql-admin
> Is there anybody using this for large DB's? Anything larger than a
> couple hundred GB, it would be impractical to make full backups
> everyday. Anyone out there using this for large DB's, if so I'd love to
> hear how they are dealing with backups.
You might want to have a look at this:
http://www.postgresql.org/docs/8.0/static/backup-online.html
-j
--
Jay A. Kreibich | CommTech, Emrg Net Tech Svcs
jak@uiuc.edu | Campus IT & Edu Svcs
<http://www.uiuc.edu/~jak; | University of Illinois at U/C
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
@ 2005-03-23 21:15 Jason Minion <jason.minion@sigler.com>
0 siblings, 0 replies; 52+ messages in thread
From: Jason Minion @ 2005-03-23 21:15 UTC (permalink / raw)
To: Joseph M. Day <jday@gisolutions.us>; Naomi Walker <nwalke@eldocomp.com>; +Cc: pgsql-admin
If you are running version 8, you may want to look into the WAL archiving:
http://www.postgresql.org/docs/8.0/interactive/backup-online.html
That would form the basis of your incremental backup strategy. I haven't had the joy of using them myself however, and do not know of any tools to make it more convenient, and a quick breeze through pgfoundry didn't find much either.
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Joseph M. Day
Sent: Wednesday, March 23, 2005 3:02 PM
To: 'Naomi Walker'
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Backup
Joseph M. Day wrote:
>> I am trying to convert a MSSQL DB thats roughly 45GB, to Postgres. I
>> am
>> trying to find the equivalent of Full / Incremental / Differential
>> backups. It looks like pg_dump is the equivalent of a full backup,
but
>> how do I keep the equivalent of a Incremental, or Differential
backup.
>>
>> To keep the same functionality, I will need a full backup once a
week,
>> and a differential once a day.
>>
>At this time, there is nothing less than full backups.
--
Thanks Naomi.
Is there anybody using this for large DB's? Anything larger than a
couple hundred GB, it would be impractical to make full backups
everyday. Anyone out there using this for large DB's, if so I'd love to
hear how they are dealing with backups.
Joe,
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
@ 2005-03-25 13:30 John Jensen <jrj@ft.fo>
0 siblings, 0 replies; 52+ messages in thread
From: John Jensen @ 2005-03-25 13:30 UTC (permalink / raw)
To: jday@gisolutions.us; pgsql-admin
Hi,
I have a 61Gig base at the moment and do a full online backup each
night.
It's not really that much of a strain so I haven't bothered with cooking
up a scheme for differential backups. Using my simple scripts it takes
one hour and in my case I end up with 2.5Gigs (compressed) worth of
backup files. The backup claims two cpu's for the hour that the job runs
but on a multi-cpu box it's not that much trouble.
My scripts are:
#! /bin/sh
if test $# -lt 2; then
echo "Usage: dbbackup <basename> <filename>"
else
/home/postgres/postgresql/bin/pg_dump -h $HOSTNAME $1 | gzip -f - |
split --bytes 600m - $2.
fi
and
if test $# -lt 2; then
echo "Usage: dbrestore <basename> <filename>"
else
cat $2.* | gzip -d -f - | /home/postgres/postgresql/bin/psql -h
$HOSTNAME -f - $1
fi
Cheers,
John
>>> "Joseph M. Day" <jday@gisolutions.us> 03/23/05 8:41 PM >>>
It looks like pg_dump is the equivalent of a full backup, but
how do I keep the equivalent of a Incremental, or Differential backup.
To keep the same functionality, I will need a full backup once a week,
and a differential once a day.
^ permalink raw reply [nested|flat] 52+ messages in thread
* backup
@ 2005-12-15 01:00 Muhammad Farid <farid13@gmail.com>
2005-12-15 13:37 ` Re: backup Devrim GUNDUZ <devrim@commandprompt.com>
0 siblings, 1 reply; 52+ messages in thread
From: Muhammad Farid @ 2005-12-15 01:00 UTC (permalink / raw)
To: pgsql-admin
Hi,
I have installed Suse Linux Opeb Excchange server and its running using
postgresql-7.2.2-35. And my problem here is i cant log in to the database
itself using command pgsql < db name > . Is there another command to log in
to the database ?I hope somebody will help me on this problem . And also
please teach me what is the command to manually backup the database in
postgresql ?
Thanks,
Farid
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2005-12-15 01:00 backup Muhammad Farid <farid13@gmail.com>
@ 2005-12-15 13:37 ` Devrim GUNDUZ <devrim@commandprompt.com>
2005-12-15 16:52 ` Re: backup Dianne Yumul <dianne@wellsgaming.com>
0 siblings, 1 reply; 52+ messages in thread
From: Devrim GUNDUZ @ 2005-12-15 13:37 UTC (permalink / raw)
To: Muhammad Farid <farid13@gmail.com>; +Cc: pgsql-admin
Hi,
On Thu, 2005-12-15 at 09:00 +0800, Muhammad Farid wrote:
> I have installed Suse Linux Opeb Excchange server and its running
> using postgresql-7.2.2-35. And my problem here is i cant log in to the
> database itself using command pgsql < db name > .
What kind of an error message you get?
> And also please teach me what is the command to manually backup the
> database in postgresql ?
Use pg_dump.
BTW... Your PostgreSQL version is outdated and is not supported by
community (I'm not sure whether SuSE supports it or not). You should
update to a newer version.
Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2005-12-15 01:00 backup Muhammad Farid <farid13@gmail.com>
2005-12-15 13:37 ` Re: backup Devrim GUNDUZ <devrim@commandprompt.com>
@ 2005-12-15 16:52 ` Dianne Yumul <dianne@wellsgaming.com>
0 siblings, 0 replies; 52+ messages in thread
From: Dianne Yumul @ 2005-12-15 16:52 UTC (permalink / raw)
To: pgsql-admin; +Cc: Muhammad Farid <farid13@gmail.com>
>> database itself using command pgsql < db name > .
It should be psql <db_name> (not pgsql), at least on versions greater
than 7.3. And I agree, postgresql 7.2.2 is pretty outdated.
hope this helps.
On Dec 15, 2005, at 5:37 AM, Devrim GUNDUZ wrote:
> Hi,
>
> On Thu, 2005-12-15 at 09:00 +0800, Muhammad Farid wrote:
>
>> I have installed Suse Linux Opeb Excchange server and its running
>> using postgresql-7.2.2-35. And my problem here is i cant log in to the
>> database itself using command pgsql < db name > .
>
> What kind of an error message you get?
>
>> And also please teach me what is the command to manually backup the
>> database in postgresql ?
>
> Use pg_dump.
>
> BTW... Your PostgreSQL version is outdated and is not supported by
> community (I'm not sure whether SuSE supports it or not). You should
> update to a newer version.
>
> Regards,
> --
> The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
^ permalink raw reply [nested|flat] 52+ messages in thread
* Backup
@ 2006-12-13 04:43 Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Eduardo J. Ortega @ 2006-12-13 04:43 UTC (permalink / raw)
To: pgsql-admin
Hi there:
Are there any nice (official or third party) backup utilities for postgres? I
have a database which is several GB, so pg_dumping it to file and then
bzipping2 every hour is not really the way to go. I've read a little about
using WAL for incremental backup, but it sounds a little complicated and
*very* user-error prone.
(Not sure if this is the right place for it, but i really think that PG's
developers should consider including a viable backup utility in the next
version)
thanks.
--
Eduardo J. Ortega - Linux user #222873
"No fake - I'm a big fan of konqueror, and I use it for everything." -- Linus
Torvalds
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
@ 2006-12-13 07:39 ` Shoaib Mir <shoaibmir@gmail.com>
2006-12-13 10:51 ` Re: Backup Eduardo J. Ortega <ejortegau@cable.net.co>
0 siblings, 1 reply; 52+ messages in thread
From: Shoaib Mir @ 2006-12-13 07:39 UTC (permalink / raw)
To: Eduardo J. Ortega <ejortegau@cable.net.co>; +Cc: pgsql-admin
To me PITR looks like a very nice solution for incremental backup and even
they can serve as a warm standby. What exactly are the complications you see
with WAL archiving?
---------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
>
> Hi there:
>
> Are there any nice (official or third party) backup utilities for
> postgres? I
> have a database which is several GB, so pg_dumping it to file and then
> bzipping2 every hour is not really the way to go. I've read a little about
> using WAL for incremental backup, but it sounds a little complicated and
> *very* user-error prone.
>
> (Not sure if this is the right place for it, but i really think that PG's
> developers should consider including a viable backup utility in the next
> version)
>
> thanks.
>
> --
> Eduardo J. Ortega - Linux user #222873
> "No fake - I'm a big fan of konqueror, and I use it for everything." --
> Linus
> Torvalds
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
@ 2006-12-13 10:51 ` Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 11:21 ` Re: Backup Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
2006-12-13 11:22 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
0 siblings, 2 replies; 52+ messages in thread
From: Eduardo J. Ortega @ 2006-12-13 10:51 UTC (permalink / raw)
To: pgsql-admin
Hi:
Well, I don't really like the fact that admin has to specify the archiving and
restoring command; an error here (a lack of -i in cp, for example) may render
the backup useless. In addition, the backup is performed only everytime the
WAL file is filled; i need to take consistent backups every hour or so, and I
am not sure if that time represents more or less than a WAL file ( i could
still measure that, i guess). Finally, as I understand, the WAL backup method
works like this:
1) Take full base FS backup
2) get some way to copy WAL files
If this is it, then I'll end up with an old level zero (i.e. full, base )
backup and A LOT of level 1 (i.e. transaction log) backup. I think it should
be more like it's for Informix, where you ask the database to perform an
online level 0 backup (base); after this, it stores transaction logs on disk,
which you can archive with level 1 backup. Then, say everyonce in a week, you
get another level 0 backup, and the database clears the already-archived logs
from disk and starts all over.
I guess this could be achieved with PG, but it requieres considerably more
steps (pg_start_backup, pg_stop_backup, manually cleaning old log files which
could be an error point), or I am getting something wrong. Besides, why do
you need to tell the database to stop the backup? shouldn't it stop by itself
when there's no more information to be archived?
Perhaps if any of you has this method working, you could provide me with your
archiving and restoring commands as well as a description of the whole
process the way you implemented it.
Thanks,
Eduardo.
On Wednesday 13 December 2006 02:39, Shoaib Mir wrote:
> To me PITR looks like a very nice solution for incremental backup and even
> they can serve as a warm standby. What exactly are the complications you
> see with WAL archiving?
>
> ---------------
> Shoaib Mir
> EnterpriseDB (www.enterprisedb.com)
>
> On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
> > Hi there:
> >
> > Are there any nice (official or third party) backup utilities for
> > postgres? I
> > have a database which is several GB, so pg_dumping it to file and then
> > bzipping2 every hour is not really the way to go. I've read a little
> > about using WAL for incremental backup, but it sounds a little
> > complicated and *very* user-error prone.
> >
> > (Not sure if this is the right place for it, but i really think that PG's
> > developers should consider including a viable backup utility in the next
> > version)
> >
> > thanks.
> >
> > --
> > Eduardo J. Ortega - Linux user #222873
> > "No fake - I'm a big fan of konqueror, and I use it for everything." --
> > Linus
> > Torvalds
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: Don't 'kill -9' the postmaster
--
Eduardo J. Ortega - Linux user #222873
"No fake - I'm a big fan of konqueror, and I use it for everything." -- Linus
Torvalds
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
2006-12-13 10:51 ` Re: Backup Eduardo J. Ortega <ejortegau@cable.net.co>
@ 2006-12-13 11:21 ` Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
2006-12-14 10:28 ` Re: Backup Eduardo J. Ortega <ejortegau@cable.net.co>
1 sibling, 1 reply; 52+ messages in thread
From: Andy Shellam (Mailing Lists) @ 2006-12-13 11:21 UTC (permalink / raw)
To: pgsql-admin
This could be implemented as a fairly simple script that does:
- Specify a base backup name (e.g. with date/time)
- Connect to postgres database
- Issue pg_start_backup('base backup name')
- Tar the data cluster directory, excluding pg_xlog
- Issue pg_stop_backup
- Compress the created archive
- Move the created archive to the backup history folder (or tape-drive etc)
- Find the date/time stamp of the latest ".backup" file in the xlog archive
- Remove any WAL files created earlier than this ".backup" file
(excluding the first WAL file needed - specified as START_WAL_LOCATION
(within the .backup file)
This process runs on our main PGSQL server at 2:00 in the morning and
finishes within 4 minutes (on a 2GB database), and our backups can
restore reliably - we have a base backup from 2:00am, and WAL files
maintained throughout the day. We're getting a new WAL file archived
roughly every 3-6 minutes, so should our server crash (or we feel the
need) we can restore up to 6 minutes ago.
The archive_command is just a simple copy - "cp %p /path/to/archive/%f"
There's really nothing difficult, it puts you (the administrator) in
control of every aspect of your backup which is a good thing.
"If this is it, then I'll end up with an old level zero (i.e. full, base )
backup and A LOT of level 1 (i.e. transaction log) backup. I think it should
be more like it's for Informix, where you ask the database to perform an
online level 0 backup (base); after this, it stores transaction logs on disk,
which you can archive with level 1 backup. Then, say everyonce in a week, you
get another level 0 backup, and the database clears the already-archived logs
from disk and starts all over."
This to me is exactly the same approach. If you really want to, you can
tell PostgreSQL to do an online backup, wait a week (saving all WAL
logs), then perform another online backup and remove the previous week's
log files - it's just you'll end up with a lot of log files (dependent
on transaction frequency and archive settings.) You don't have to have
one base backup and then a ton of log files, because it'll take you
forever to restore it, in fact the more often you perform a base backup
the better (I had to restore a 2GB database a while backup, with a
week's worth of WAL files, and it took 10 hours!)
"a lack of -i in cp, for example"
FWIW, -i in copy won't render a backup useless - only if the file to be
archived has already been archived (in which case it stands a chance
it's the same file anyway as PG rotates/recycles WAL file numbers.)
Hope this goes some way to helping you out,
Andy.
Eduardo J. Ortega wrote:
> Hi:
>
> Well, I don't really like the fact that admin has to specify the archiving and
> restoring command; an error here (a lack of -i in cp, for example) may render
> the backup useless. In addition, the backup is performed only everytime the
> WAL file is filled; i need to take consistent backups every hour or so, and I
> am not sure if that time represents more or less than a WAL file ( i could
> still measure that, i guess). Finally, as I understand, the WAL backup method
> works like this:
> 1) Take full base FS backup
> 2) get some way to copy WAL files
>
> If this is it, then I'll end up with an old level zero (i.e. full, base )
> backup and A LOT of level 1 (i.e. transaction log) backup. I think it should
> be more like it's for Informix, where you ask the database to perform an
> online level 0 backup (base); after this, it stores transaction logs on disk,
> which you can archive with level 1 backup. Then, say everyonce in a week, you
> get another level 0 backup, and the database clears the already-archived logs
> from disk and starts all over.
>
> I guess this could be achieved with PG, but it requieres considerably more
> steps (pg_start_backup, pg_stop_backup, manually cleaning old log files which
> could be an error point), or I am getting something wrong. Besides, why do
> you need to tell the database to stop the backup? shouldn't it stop by itself
> when there's no more information to be archived?
>
> Perhaps if any of you has this method working, you could provide me with your
> archiving and restoring commands as well as a description of the whole
> process the way you implemented it.
>
> Thanks,
>
> Eduardo.
>
> On Wednesday 13 December 2006 02:39, Shoaib Mir wrote:
>
>> To me PITR looks like a very nice solution for incremental backup and even
>> they can serve as a warm standby. What exactly are the complications you
>> see with WAL archiving?
>>
>> ---------------
>> Shoaib Mir
>> EnterpriseDB (www.enterprisedb.com)
>>
>> On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
>>
>>> Hi there:
>>>
>>> Are there any nice (official or third party) backup utilities for
>>> postgres? I
>>> have a database which is several GB, so pg_dumping it to file and then
>>> bzipping2 every hour is not really the way to go. I've read a little
>>> about using WAL for incremental backup, but it sounds a little
>>> complicated and *very* user-error prone.
>>>
>>> (Not sure if this is the right place for it, but i really think that PG's
>>> developers should consider including a viable backup utility in the next
>>> version)
>>>
>>> thanks.
>>>
>>> --
>>> Eduardo J. Ortega - Linux user #222873
>>> "No fake - I'm a big fan of konqueror, and I use it for everything." --
>>> Linus
>>> Torvalds
>>>
>>> ---------------------------(end of broadcast)---------------------------
>>> TIP 2: Don't 'kill -9' the postmaster
>>>
>
>
--
Andy Shellam
NetServe Support Team
the Mail Network
"an alternative in a standardised world"
p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
2006-12-13 10:51 ` Re: Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 11:21 ` Re: Backup Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
@ 2006-12-14 10:28 ` Eduardo J. Ortega <ejortegau@cable.net.co>
0 siblings, 0 replies; 52+ messages in thread
From: Eduardo J. Ortega @ 2006-12-14 10:28 UTC (permalink / raw)
To: pgsql-admin
Thanks for this hint, I'll try to do this. Is there any change you could send
me your 02:00 AM script so that i use something *I know* is already working?
Perhaps off the mailing list, since maybe not everyone will enjoy code on
their mail.
Thanks.
On Wednesday 13 December 2006 06:21, Andy Shellam (Mailing Lists) wrote:
> This could be implemented as a fairly simple script that does:
>
> - Specify a base backup name (e.g. with date/time)
> - Connect to postgres database
> - Issue pg_start_backup('base backup name')
> - Tar the data cluster directory, excluding pg_xlog
> - Issue pg_stop_backup
> - Compress the created archive
> - Move the created archive to the backup history folder (or tape-drive etc)
> - Find the date/time stamp of the latest ".backup" file in the xlog archive
> - Remove any WAL files created earlier than this ".backup" file
> (excluding the first WAL file needed - specified as START_WAL_LOCATION
> (within the .backup file)
>
> This process runs on our main PGSQL server at 2:00 in the morning and
> finishes within 4 minutes (on a 2GB database), and our backups can
> restore reliably - we have a base backup from 2:00am, and WAL files
> maintained throughout the day. We're getting a new WAL file archived
> roughly every 3-6 minutes, so should our server crash (or we feel the
> need) we can restore up to 6 minutes ago.
>
> The archive_command is just a simple copy - "cp %p /path/to/archive/%f"
>
> There's really nothing difficult, it puts you (the administrator) in
> control of every aspect of your backup which is a good thing.
>
> "If this is it, then I'll end up with an old level zero (i.e. full, base )
> backup and A LOT of level 1 (i.e. transaction log) backup. I think it
> should be more like it's for Informix, where you ask the database to
> perform an online level 0 backup (base); after this, it stores transaction
> logs on disk, which you can archive with level 1 backup. Then, say
> everyonce in a week, you get another level 0 backup, and the database
> clears the already-archived logs from disk and starts all over."
>
>
> This to me is exactly the same approach. If you really want to, you can
> tell PostgreSQL to do an online backup, wait a week (saving all WAL
> logs), then perform another online backup and remove the previous week's
> log files - it's just you'll end up with a lot of log files (dependent
> on transaction frequency and archive settings.) You don't have to have
> one base backup and then a ton of log files, because it'll take you
> forever to restore it, in fact the more often you perform a base backup
> the better (I had to restore a 2GB database a while backup, with a
> week's worth of WAL files, and it took 10 hours!)
>
> "a lack of -i in cp, for example"
>
> FWIW, -i in copy won't render a backup useless - only if the file to be
> archived has already been archived (in which case it stands a chance
> it's the same file anyway as PG rotates/recycles WAL file numbers.)
>
> Hope this goes some way to helping you out,
>
> Andy.
>
> Eduardo J. Ortega wrote:
> > Hi:
> >
> > Well, I don't really like the fact that admin has to specify the
> > archiving and restoring command; an error here (a lack of -i in cp, for
> > example) may render the backup useless. In addition, the backup is
> > performed only everytime the WAL file is filled; i need to take
> > consistent backups every hour or so, and I am not sure if that time
> > represents more or less than a WAL file ( i could still measure that, i
> > guess). Finally, as I understand, the WAL backup method works like this:
> > 1) Take full base FS backup
> > 2) get some way to copy WAL files
> >
> > If this is it, then I'll end up with an old level zero (i.e. full, base )
> > backup and A LOT of level 1 (i.e. transaction log) backup. I think it
> > should be more like it's for Informix, where you ask the database to
> > perform an online level 0 backup (base); after this, it stores
> > transaction logs on disk, which you can archive with level 1 backup.
> > Then, say everyonce in a week, you get another level 0 backup, and the
> > database clears the already-archived logs from disk and starts all over.
> >
> > I guess this could be achieved with PG, but it requieres considerably
> > more steps (pg_start_backup, pg_stop_backup, manually cleaning old log
> > files which could be an error point), or I am getting something wrong.
> > Besides, why do you need to tell the database to stop the backup?
> > shouldn't it stop by itself when there's no more information to be
> > archived?
> >
> > Perhaps if any of you has this method working, you could provide me with
> > your archiving and restoring commands as well as a description of the
> > whole process the way you implemented it.
> >
> > Thanks,
> >
> > Eduardo.
> >
> > On Wednesday 13 December 2006 02:39, Shoaib Mir wrote:
> >> To me PITR looks like a very nice solution for incremental backup and
> >> even they can serve as a warm standby. What exactly are the
> >> complications you see with WAL archiving?
> >>
> >> ---------------
> >> Shoaib Mir
> >> EnterpriseDB (www.enterprisedb.com)
> >>
> >> On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
> >>> Hi there:
> >>>
> >>> Are there any nice (official or third party) backup utilities for
> >>> postgres? I
> >>> have a database which is several GB, so pg_dumping it to file and then
> >>> bzipping2 every hour is not really the way to go. I've read a little
> >>> about using WAL for incremental backup, but it sounds a little
> >>> complicated and *very* user-error prone.
> >>>
> >>> (Not sure if this is the right place for it, but i really think that
> >>> PG's developers should consider including a viable backup utility in
> >>> the next version)
> >>>
> >>> thanks.
> >>>
> >>> --
> >>> Eduardo J. Ortega - Linux user #222873
> >>> "No fake - I'm a big fan of konqueror, and I use it for everything." --
> >>> Linus
> >>> Torvalds
> >>>
> >>> ---------------------------(end of
> >>> broadcast)--------------------------- TIP 2: Don't 'kill -9' the
> >>> postmaster
--
Eduardo J. Ortega - Linux user #222873
"No fake - I'm a big fan of konqueror, and I use it for everything." -- Linus
Torvalds
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Re: Backup Shoaib Mir <shoaibmir@gmail.com>
2006-12-13 10:51 ` Re: Backup Eduardo J. Ortega <ejortegau@cable.net.co>
@ 2006-12-13 11:22 ` Shoaib Mir <shoaibmir@gmail.com>
1 sibling, 0 replies; 52+ messages in thread
From: Shoaib Mir @ 2006-12-13 11:22 UTC (permalink / raw)
To: Eduardo J. Ortega <ejortegau@cable.net.co>; +Cc: pgsql-admin
>> In addition, the backup is performed only everytime the WAL file is
filled; i need to take >>consistent backups every hour or so
You have the archive_timeout (
http://www.postgresql.org/docs/8.2/static/runtime-config-wal.html) option
for that in PG 8.2 to achieve similar functionality
>>Well, I don't really like the fact that admin has to specify the archiving
and
>>restoring command; an error here (a lack of -i in cp, for example) may
render
>>the backup useless
You dont have to take the base backup again and again, just will be needing
the WAL archives to restore to a certain point, but if still you want to
take the backup you can easily write a cron job and schedule it.
>>If this is it, then I'll end up with an old level zero (i.e. full, base )
>>backup and A LOT of level 1 (i.e. transaction log) backup. I think it
should
>>be more like it's for Informix, where you ask the database to perform an
>>online level 0 backup (base); after this, it stores transaction logs on
disk,
>>which you can archive with level 1 backup.
I think that can be also possible using something similar to warm standby (
http://www.postgresql.org/docs/8.2/static/warm-standby.html)
Hope this helps....
----------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
>
> Hi:
>
> Well, I don't really like the fact that admin has to specify the archiving
> and
> restoring command; an error here (a lack of -i in cp, for example) may
> render
> the backup useless. In addition, the backup is performed only everytime
> the
> WAL file is filled; i need to take consistent backups every hour or so,
> and I
> am not sure if that time represents more or less than a WAL file ( i could
> still measure that, i guess). Finally, as I understand, the WAL backup
> method
> works like this:
> 1) Take full base FS backup
> 2) get some way to copy WAL files
>
> If this is it, then I'll end up with an old level zero (i.e. full, base )
> backup and A LOT of level 1 (i.e. transaction log) backup. I think it
> should
> be more like it's for Informix, where you ask the database to perform an
> online level 0 backup (base); after this, it stores transaction logs on
> disk,
> which you can archive with level 1 backup. Then, say everyonce in a week,
> you
> get another level 0 backup, and the database clears the already-archived
> logs
> from disk and starts all over.
>
> I guess this could be achieved with PG, but it requieres considerably more
> steps (pg_start_backup, pg_stop_backup, manually cleaning old log files
> which
> could be an error point), or I am getting something wrong. Besides, why do
> you need to tell the database to stop the backup? shouldn't it stop by
> itself
> when there's no more information to be archived?
>
> Perhaps if any of you has this method working, you could provide me with
> your
> archiving and restoring commands as well as a description of the whole
> process the way you implemented it.
>
> Thanks,
>
> Eduardo.
>
> On Wednesday 13 December 2006 02:39, Shoaib Mir wrote:
> > To me PITR looks like a very nice solution for incremental backup and
> even
> > they can serve as a warm standby. What exactly are the complications you
> > see with WAL archiving?
> >
> > ---------------
> > Shoaib Mir
> > EnterpriseDB (www.enterprisedb.com)
> >
> > On 12/13/06, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
> > > Hi there:
> > >
> > > Are there any nice (official or third party) backup utilities for
> > > postgres? I
> > > have a database which is several GB, so pg_dumping it to file and then
> > > bzipping2 every hour is not really the way to go. I've read a little
> > > about using WAL for incremental backup, but it sounds a little
> > > complicated and *very* user-error prone.
> > >
> > > (Not sure if this is the right place for it, but i really think that
> PG's
> > > developers should consider including a viable backup utility in the
> next
> > > version)
> > >
> > > thanks.
> > >
> > > --
> > > Eduardo J. Ortega - Linux user #222873
> > > "No fake - I'm a big fan of konqueror, and I use it for everything."
> --
> > > Linus
> > > Torvalds
> > >
> > > ---------------------------(end of
> broadcast)---------------------------
> > > TIP 2: Don't 'kill -9' the postmaster
>
> --
> Eduardo J. Ortega - Linux user #222873
> "No fake - I'm a big fan of konqueror, and I use it for everything." --
> Linus
> Torvalds
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
^ permalink raw reply [nested|flat] 52+ messages in thread
* Backup
@ 2008-01-24 19:08 Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 00:47 ` Re: Backup Scott Marlowe <scott.marlowe@gmail.com>
2008-01-30 04:15 ` Re: Backup Vishal Arora <aroravishal22@hotmail.com>
0 siblings, 3 replies; 52+ messages in thread
From: Dominic Carlucci @ 2008-01-24 19:08 UTC (permalink / raw)
To: pgsql-general@postgresql.org; pgsql-admin; +Cc: carlucci@cae.ca
Hi,
We have a center in Europe who has just started to use PostgreSQL
and was asking me if there are any Symantec product or other products
that backup this type of database. We presently run VERITAS ver9.1 on
windows2003 server. What is being used by users out there now. We are
thinking of upgrading to the latest Symantec backup exec software but am
not sure if this version does backup PostgreSQL. When called for support
they told me to go to the Symantec site and search the compatibility
list. I didn't find anything dealing with PostgreSQL database.
Any answer would help me simplify my backup situation.
Thanks,
Dominic Carlucci
Production Control Analyst
CAE Inc.
8585 Cote de Liesse
St. Laurent, Quebec H4T 1G6
(514)341-2000 #2936
Carlucci@cae.ca
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
@ 2008-01-25 00:34 ` Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2 siblings, 1 reply; 52+ messages in thread
From: Phillip Smith @ 2008-01-25 00:34 UTC (permalink / raw)
To: 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; +Cc: carlucci@cae.ca
> We have a center in Europe who has just started to use PostgreSQL and was
> asking me if there are any Symantec product or other products that backup
> this type of database.
It doesn't appear to. I've just been through the whole rigmarole of
BackupExec for some Windows Servers, and I couldn't find anything to deal
with PostgreSQL.
Just dump Postgres to the File System and backup that dump. Depends on what
your Recovery Point requirements are.
THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
*******************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
e-mail.
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
@ 2008-01-25 09:21 ` Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
0 siblings, 1 reply; 52+ messages in thread
From: Simon Riggs @ 2008-01-25 09:21 UTC (permalink / raw)
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>; +Cc: 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Fri, 2008-01-25 at 11:34 +1100, Phillip Smith wrote:
> > We have a center in Europe who has just started to use PostgreSQL and was
> > asking me if there are any Symantec product or other products that backup
> > this type of database.
>
> It doesn't appear to.
The design of the PITR system allows a product-agnostic backup. Anything
that can backup a file can backup PostgreSQL. There is no need for
special certifications of hologram logos.
You may need to write a few lines of script to do it, but that's not a
problem surely?
So you can use pg_dump or PITR, as you choose.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
@ 2008-01-31 12:21 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
0 siblings, 1 reply; 52+ messages in thread
From: Chander Ganesan @ 2008-01-31 12:21 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>; Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
Simon Riggs wrote:
> On Fri, 2008-01-25 at 11:34 +1100, Phillip Smith wrote:
>
>>> We have a center in Europe who has just started to use PostgreSQL and was
>>> asking me if there are any Symantec product or other products that backup
>>> this type of database.
>>>
>> It doesn't appear to.
>>
>
> The design of the PITR system allows a product-agnostic backup. Anything
> that can backup a file can backup PostgreSQL. There is no need for
> special certifications of hologram logos.
>
> You may need to write a few lines of script to do it, but that's not a
> problem surely?
>
> So you can use pg_dump or PITR, as you choose.
>
If you don't mind if you lose some transactions you can also use file
system snapshotting....which would work just as well as pg_dump, and
probably have less impact on the running database (assuming you had
decent enough hardware).
So long as the product you are using can snapshot the file system prior
to performing a backup, you can use just about any product (without
having to really do much/any work). When you restore a snapshotted file
system that contains your postgresql database, postgresql (on restart)
will enter auto-recovery mode and recover (as it does in the case of the
crash) to the last transaction that was completed successfully prior to
the snapshot being created. Note that this would only work if all your
tablespaces were on the same file system, and would be unable to "roll
forward" using WAL files generated after the backup.
However, you should keep in mind that - like a pg_dump - you won't be
able to perform PITR recovery from such a backup. Also, the recovery
time may be non-trivial depending on your WAL settings.
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
Phone: 877-258-8987/919-463-0999
http://www.otg-nc.com
As me about Expert PostgreSQL & PostGIS Training delivered worldwide.
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
@ 2008-01-31 13:28 ` Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 15:00 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
0 siblings, 2 replies; 52+ messages in thread
From: Simon Riggs @ 2008-01-31 13:28 UTC (permalink / raw)
To: Chander Ganesan <chander@otg-nc.com>; +Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>; 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Thu, 2008-01-31 at 07:21 -0500, Chander Ganesan wrote:
> If you don't mind if you lose some transactions
That sentence has no place in any discussion about "backup" because the
risk is not just a few transactions, it is a corrupt and inconsistent
database from which both old and new data would be inaccessible.
As far as I am concerned, if any Postgres user loses data then we're all
responsible.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
@ 2008-01-31 14:34 ` Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Re: [GENERAL] Backup Magnus Hagander <magnus@hagander.net>
1 sibling, 1 reply; 52+ messages in thread
From: Martijn van Oosterhout @ 2008-01-31 14:34 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Chander Ganesan <chander@otg-nc.com>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
> That sentence has no place in any discussion about "backup" because the
> risk is not just a few transactions, it is a corrupt and inconsistent
> database from which both old and new data would be inaccessible.
Hmm? I thought the whole point of a filesystem snapshot was that it's
the same as if the system crashed. And I was fairly sure we could
recover from that...
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
> -- John F Kennedy
Attachments:
signature.asc (application/pgp-signature, 188B) download
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
@ 2008-01-31 14:43 ` Magnus Hagander <magnus@hagander.net>
2008-01-31 15:02 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
0 siblings, 1 reply; 52+ messages in thread
From: Magnus Hagander @ 2008-01-31 14:43 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; Chander Ganesan <chander@otg-nc.com>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
> > That sentence has no place in any discussion about "backup" because the
> > risk is not just a few transactions, it is a corrupt and inconsistent
> > database from which both old and new data would be inaccessible.
>
> Hmm? I thought the whole point of a filesystem snapshot was that it's
> the same as if the system crashed. And I was fairly sure we could
> recover from that...
That was my assumption as well. *Assuming* that the filesystem snapshot is
consistent. There are a bunch of solutions that don't do consistent
snapshots between different partitions, so if your WAL or one tablespace is
on a different partition, you'll get corruption anyway... (seen this in
Big Commercial Database, so that's not a pg problem)
//Magnus
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Re: [GENERAL] Backup Magnus Hagander <magnus@hagander.net>
@ 2008-01-31 15:02 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 15:58 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-02-06 13:29 ` Re: [GENERAL] Backup Hannes Dorbath <light@theendofthetunnel.de>
0 siblings, 2 replies; 52+ messages in thread
From: Chander Ganesan @ 2008-01-31 15:02 UTC (permalink / raw)
To: Magnus Hagander <magnus@hagander.net>; +Cc: Simon Riggs <simon@2ndquadrant.com>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
Magnus Hagander wrote:
> On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
>
>> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
>>
>>> That sentence has no place in any discussion about "backup" because the
>>> risk is not just a few transactions, it is a corrupt and inconsistent
>>> database from which both old and new data would be inaccessible.
>>>
>> Hmm? I thought the whole point of a filesystem snapshot was that it's
>> the same as if the system crashed. And I was fairly sure we could
>> recover from that...
>>
>
> That was my assumption as well. *Assuming* that the filesystem snapshot is
> consistent. There are a bunch of solutions that don't do consistent
> snapshots between different partitions, so if your WAL or one tablespace is
> on a different partition, you'll get corruption anyway... (seen this in
> Big Commercial Database, so that's not a pg problem)
>
Agreed. That's why I made it a point to mention that all of your
tablespaces should be on the same file system... In hindsight, I should
have also stated that your WAL logs should be on the same file system as
well...
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Re: [GENERAL] Backup Magnus Hagander <magnus@hagander.net>
2008-01-31 15:02 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
@ 2008-01-31 15:58 ` Simon Riggs <simon@2ndquadrant.com>
1 sibling, 0 replies; 52+ messages in thread
From: Simon Riggs @ 2008-01-31 15:58 UTC (permalink / raw)
To: Chander Ganesan <chander@otg-nc.com>; +Cc: Magnus Hagander <magnus@hagander.net>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Thu, 2008-01-31 at 10:02 -0500, Chander Ganesan wrote:
> Magnus Hagander wrote:
> > On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> >
> >> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
> >>
> >>> That sentence has no place in any discussion about "backup" because the
> >>> risk is not just a few transactions, it is a corrupt and inconsistent
> >>> database from which both old and new data would be inaccessible.
> >>>
> >> Hmm? I thought the whole point of a filesystem snapshot was that it's
> >> the same as if the system crashed. And I was fairly sure we could
> >> recover from that...
> >>
> >
> > That was my assumption as well. *Assuming* that the filesystem snapshot is
> > consistent. There are a bunch of solutions that don't do consistent
> > snapshots between different partitions, so if your WAL or one tablespace is
> > on a different partition, you'll get corruption anyway... (seen this in
> > Big Commercial Database, so that's not a pg problem)
> >
> Agreed. That's why I made it a point to mention that all of your
> tablespaces should be on the same file system... In hindsight, I should
> have also stated that your WAL logs should be on the same file system as
> well...
I think we all understand and agree, I just start twitching when anyone
talks about it being OK to lose transactions when backing up. You meant
the ones currently in progress, not the ones already committed and on
disk.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Re: [GENERAL] Backup Magnus Hagander <magnus@hagander.net>
2008-01-31 15:02 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
@ 2008-02-06 13:29 ` Hannes Dorbath <light@theendofthetunnel.de>
2008-02-06 13:49 ` Re: [GENERAL] Backup Hannes Dorbath <light@theendofthetunnel.de>
1 sibling, 1 reply; 52+ messages in thread
From: Hannes Dorbath @ 2008-02-06 13:29 UTC (permalink / raw)
To: Chander Ganesan <chander@otg-nc.com>
Chander Ganesan wrote:
> Magnus Hagander wrote:
>> On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
>>
>>> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
>>>
>>>> That sentence has no place in any discussion about "backup" because the
>>>> risk is not just a few transactions, it is a corrupt and inconsistent
>>>> database from which both old and new data would be inaccessible.
>>>>
>>> Hmm? I thought the whole point of a filesystem snapshot was that it's
>>> the same as if the system crashed. And I was fairly sure we could
>>> recover from that...
>>>
>>
>> That was my assumption as well. *Assuming* that the filesystem
>> snapshot is
>> consistent. There are a bunch of solutions that don't do consistent
>> snapshots between different partitions, so if your WAL or one
>> tablespace is
>> on a different partition, you'll get corruption anyway... (seen this in
>> Big Commercial Database, so that's not a pg problem)
>>
> Agreed. That's why I made it a point to mention that all of your
> tablespaces should be on the same file system... In hindsight, I should
> have also stated that your WAL logs should be on the same file system as
One more reason to consider using Solaris ZFS -- it does consistent
snapshots across all file systems.
--
Best regards,
Hannes Dorbath
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Re: [GENERAL] Backup Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Re: [GENERAL] Backup Magnus Hagander <magnus@hagander.net>
2008-01-31 15:02 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-02-06 13:29 ` Re: [GENERAL] Backup Hannes Dorbath <light@theendofthetunnel.de>
@ 2008-02-06 13:49 ` Hannes Dorbath <light@theendofthetunnel.de>
0 siblings, 0 replies; 52+ messages in thread
From: Hannes Dorbath @ 2008-02-06 13:49 UTC (permalink / raw)
To: pgsql-admin; +Cc: Chander Ganesan <chander@otg-nc.com>
Hannes Dorbath wrote:
> Chander Ganesan wrote:
>> Magnus Hagander wrote:
>>> On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
>>>
>>>> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
>>>>
>>>>> That sentence has no place in any discussion about "backup" because
>>>>> the
>>>>> risk is not just a few transactions, it is a corrupt and inconsistent
>>>>> database from which both old and new data would be inaccessible.
>>>>>
>>>> Hmm? I thought the whole point of a filesystem snapshot was that it's
>>>> the same as if the system crashed. And I was fairly sure we could
>>>> recover from that...
>>>>
>>>
>>> That was my assumption as well. *Assuming* that the filesystem
>>> snapshot is
>>> consistent. There are a bunch of solutions that don't do consistent
>>> snapshots between different partitions, so if your WAL or one
>>> tablespace is
>>> on a different partition, you'll get corruption anyway... (seen this in
>>> Big Commercial Database, so that's not a pg problem)
>>>
>> Agreed. That's why I made it a point to mention that all of your
>> tablespaces should be on the same file system... In hindsight, I
>> should have also stated that your WAL logs should be on the same file
>> system as
>
> One more reason to consider using Solaris ZFS -- it does consistent
> snapshots across all file systems.
In general file system snapshots are quite a pain with Linux LVM.
Even when using separate spindles for the snapshot COW area the impact
on write performance on the origin LV is still huge. You'll have a hard
time to write with more than 15MB/sec to the origin LV.
Additionally when you lost your COW device there is this nice bug in
vgreduce --removemissing that will silently delete your origin LV as
well: http://readlist.com/lists/redhat.com/linux-lvm/0/2025.html
Not to mention that LVM does not support write barriers and does mess
with any kind of stripe alignment of your file system.
--
Best regards,
Hannes Dorbath
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
@ 2008-01-31 15:00 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 15:09 ` Re: [GENERAL] Backup Alvaro Herrera <alvherre@commandprompt.com>
1 sibling, 1 reply; 52+ messages in thread
From: Chander Ganesan @ 2008-01-31 15:00 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>; Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
Simon Riggs wrote:
> On Thu, 2008-01-31 at 07:21 -0500, Chander Ganesan wrote:
>
>> If you don't mind if you lose some transactions
>>
>
> That sentence has no place in any discussion about "backup" because the
> risk is not just a few transactions, it is a corrupt and inconsistent
> database from which both old and new data would be inaccessible.
>
> As far as I am concerned, if any Postgres user loses data then we're all
> responsible.
>
I understand your point, but indicating that you can't trust a
point-in-time snapshot of the database is, IMHO, the same as saying you
can't trust PostgreSQL's automatic crash recovery, since the two are
essentially the same thing...
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 15:00 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
@ 2008-01-31 15:09 ` Alvaro Herrera <alvherre@commandprompt.com>
2008-01-31 15:48 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
0 siblings, 1 reply; 52+ messages in thread
From: Alvaro Herrera @ 2008-01-31 15:09 UTC (permalink / raw)
To: Chander Ganesan <chander@otg-nc.com>; +Cc: Simon Riggs <simon@2ndquadrant.com>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
> Simon Riggs wrote:
>> As far as I am concerned, if any Postgres user loses data then we're all
>> responsible.
Remember, our license says this software is given without any warranty
whatsoever, implicit or explicit, written or implied, given or sold,
alive or deceased.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: [GENERAL] Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Re: Backup Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Re: Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Re: [GENERAL] Backup Simon Riggs <simon@2ndquadrant.com>
2008-01-31 15:00 ` Re: [GENERAL] Backup Chander Ganesan <chander@otg-nc.com>
2008-01-31 15:09 ` Re: [GENERAL] Backup Alvaro Herrera <alvherre@commandprompt.com>
@ 2008-01-31 15:48 ` Simon Riggs <simon@2ndquadrant.com>
0 siblings, 0 replies; 52+ messages in thread
From: Simon Riggs @ 2008-01-31 15:48 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Chander Ganesan <chander@otg-nc.com>; Phillip Smith <phillip.smith@weatherbeeta.com.au>; 'Dominic Carlucci' <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Thu, 2008-01-31 at 12:09 -0300, Alvaro Herrera wrote:
> > Simon Riggs wrote:
>
> >> As far as I am concerned, if any Postgres user loses data then we're all
> >> responsible.
>
> Remember, our license says this software is given without any warranty
> whatsoever, implicit or explicit, written or implied, given or sold,
> alive or deceased.
Yes! ...I meant via the free press, not via the courts.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
@ 2008-01-25 00:47 ` Scott Marlowe <scott.marlowe@gmail.com>
2 siblings, 0 replies; 52+ messages in thread
From: Scott Marlowe @ 2008-01-25 00:47 UTC (permalink / raw)
To: Dominic Carlucci <carlucci@cae.com>; +Cc: pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
On Jan 24, 2008 1:08 PM, Dominic Carlucci <carlucci@cae.com> wrote:
>
>
> Hi,
> We have a center in Europe who has just started to use PostgreSQL and
> was asking me if there are any Symantec product or other products that
> backup this type of database. We presently run VERITAS ver9.1 on
> windows2003 server. What is being used by users out there now. We are
> thinking of upgrading to the latest Symantec backup exec software but am not
> sure if this version does backup PostgreSQL. When called for support they
> told me to go to the Symantec site and search the compatibility list. I
> didn't find anything dealing with PostgreSQL database.
> Any answer would help me simplify my backup situation.
Not sure if there's some kind of special plug in for Symantec, but
basically, you want to run pg_dump or pg_dumpall and then point
symantec to back up the file thus created.
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
@ 2008-01-30 04:15 ` Vishal Arora <aroravishal22@hotmail.com>
2008-01-30 04:27 ` Re: Backup Guido Barosio <gbarosio@gmail.com>
2 siblings, 1 reply; 52+ messages in thread
From: Vishal Arora @ 2008-01-30 04:15 UTC (permalink / raw)
To: Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; +Cc: carlucci@cae.ca
PostgreSQL has its own inbuilt mechanism for backing up the database. you can refer to the postgres manual online for more information.
http://www.postgresql.org/docs/8.2/interactive/backup.html
- Vishal
Subject: [ADMIN] BackupDate: Thu, 24 Jan 2008 14:08:26 -0500From: carlucci@cae.comTo: pgsql-general@postgresql.org; pgsql-admin@postgresql.orgCC: carlucci@cae.ca
Hi,
We have a center in Europe who has just started to use PostgreSQL and was asking me if there are any Symantec product or other products that backup this type of database. We presently run VERITAS ver9.1 on windows2003 server. What is being used by users out there now. We are thinking of upgrading to the latest Symantec backup exec software but am not sure if this version does backup PostgreSQL. When called for support they told me to go to the Symantec site and search the compatibility list. I didn't find anything dealing with PostgreSQL database.
Any answer would help me simplify my backup situation.
Thanks,
Dominic CarlucciProduction Control Analyst
CAE Inc.8585 Cote de LiesseSt. Laurent, Quebec H4T 1G6
(514)341-2000 #2936Carlucci@cae.ca
_________________________________________________________________
Tried the new MSN Messenger? It’s cool! Download now.
http://messenger.msn.com/Download/Default.aspx?mkt=en-in=
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-30 04:15 ` Re: Backup Vishal Arora <aroravishal22@hotmail.com>
@ 2008-01-30 04:27 ` Guido Barosio <gbarosio@gmail.com>
0 siblings, 0 replies; 52+ messages in thread
From: Guido Barosio @ 2008-01-30 04:27 UTC (permalink / raw)
To: Vishal Arora <aroravishal22@hotmail.com>; +Cc: Dominic Carlucci <carlucci@cae.com>; pgsql-general@postgresql.org; pgsql-admin; carlucci@cae.ca
AFAIK Dominic needs a plug-in certified by Symantec, and that is not the case.
As you may have read prior to this mail, the common way is to pg_dump
against a file, picking up that file later with BackupExec as a
regular file.
We are currently (www.globant.com) using it that way, no problems at all.
gb.-
On Jan 30, 2008 2:15 AM, Vishal Arora <aroravishal22@hotmail.com> wrote:
>
> PostgreSQL has its own inbuilt mechanism for backing up the database. you
> can refer to the postgres manual online for more information.
>
> http://www.postgresql.org/docs/8.2/interactive/backup.html
>
> - Vishal
>
>
>
>
>
> ________________________________
> Subject: [ADMIN] Backup
> Date: Thu, 24 Jan 2008 14:08:26 -0500
> From: carlucci@cae.com
> To: pgsql-general@postgresql.org; pgsql-admin@postgresql.org
> CC: carlucci@cae.ca
>
>
>
>
> Hi,
> We have a center in Europe who has just started to use PostgreSQL and
> was asking me if there are any Symantec product or other products that
> backup this type of database. We presently run VERITAS ver9.1 on
> windows2003 server. What is being used by users out there now. We are
> thinking of upgrading to the latest Symantec backup exec software but am not
> sure if this version does backup PostgreSQL. When called for support they
> told me to go to the Symantec site and search the compatibility list. I
> didn't find anything dealing with PostgreSQL database.
> Any answer would help me simplify my backup situation.
> Thanks,
>
>
> Dominic Carlucci
> Production Control Analyst
>
> CAE Inc.
> 8585 Cote de Liesse
> St. Laurent, Quebec H4T 1G6
>
> (514)341-2000 #2936
> Carlucci@cae.ca
>
>
>
>
> ________________________________
> Live the life in style with MSN Lifestyle. Check out! Try it now!
>
--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com
^ permalink raw reply [nested|flat] 52+ messages in thread
* backup
@ 2012-06-18 17:50 lohita nama <namalohita@gmail.com>
2012-06-18 17:57 ` Re: backup Kevin Grittner <Kevin.Grittner@wicourts.gov>
2012-06-18 17:59 ` Re: backup Frederiko Costa <frederiko@gmail.com>
0 siblings, 2 replies; 52+ messages in thread
From: lohita nama @ 2012-06-18 17:50 UTC (permalink / raw)
To: pgsql-admin
Hi
I am working as sql dba recently our team had oppurtunity to work on
postgres databases and i had experience on sql server and on windows
platform and now our company had postgres databases on solaris platform
can u please suggest how to take the back up of postgress databases by step
by step procudure
awaiting for your reply thanks for your help
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2012-06-18 17:50 backup lohita nama <namalohita@gmail.com>
@ 2012-06-18 17:57 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
1 sibling, 0 replies; 52+ messages in thread
From: Kevin Grittner @ 2012-06-18 17:57 UTC (permalink / raw)
To: lohita nama <namalohita@gmail.com>; pgsql-admin
lohita nama <namalohita@gmail.com> wrote:
> I am working as sql dba recently our team had oppurtunity to work
> on postgres databases and i had experience on sql server and on
> windows platform and now our company had postgres databases on
> solaris platform
>
> can u please suggest how to take the back up of postgress
> databases by step by step procudure
As a new user of PostgreSQL you may not yet have noticed how good
the manuals are. You should find what you need in this chapter:
http://www.postgresql.org/docs/current/interactive/backup.html
If you are on an older version of PostgreSQL, click the link at the
top for the version you are using.
If you still have questions after reading the manual, feel free to
post with a more specific question.
-Kevin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: backup
2012-06-18 17:50 backup lohita nama <namalohita@gmail.com>
@ 2012-06-18 17:59 ` Frederiko Costa <frederiko@gmail.com>
1 sibling, 0 replies; 52+ messages in thread
From: Frederiko Costa @ 2012-06-18 17:59 UTC (permalink / raw)
To: lohita nama <namalohita@gmail.com>; +Cc: pgsql-admin
Hi,
I would recommend this:
http://www.postgresql.org/docs/9.1/static/backup.html
Very straightforward and easy reading ...
-fred
On Mon, Jun 18, 2012 at 10:50 AM, lohita nama <namalohita@gmail.com> wrote:
> Hi
>
> I am working as sql dba recently our team had oppurtunity to work on
> postgres databases and i had experience on sql server and on windows
> platform and now our company had postgres databases on solaris platform
>
> can u please suggest how to take the back up of postgress databases by
> step by step procudure
>
> awaiting for your reply thanks for your help
>
^ permalink raw reply [nested|flat] 52+ messages in thread
* Backup
@ 2012-11-30 00:59 Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Sabry Sadiq @ 2012-11-30 00:59 UTC (permalink / raw)
To: pgsql-admin
Hi All,
Has anyone been successful in offloading the database backup from the production database to the standby database?
Kind Regards,
Sabry
Sabry Sadiq
Systems Administrator
Whispir
Level 30 360 Collins Street
Melbourne / Victoria 3000 / Australia
GPO Box 130 / Victoria 3001 / Australia
T +61 3 8630 9900 / M +61 428 571 636
F +61 3 8630 9990 / E ssadiq@whispir.com
1300 WHISPIR / 1300 944 774
www.whispir.com
This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors,virus, interception or interference.
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
@ 2012-11-30 01:10 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
0 siblings, 1 reply; 52+ messages in thread
From: Lonni J Friedman @ 2012-11-30 01:10 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; +Cc: pgsql-admin
Yes. Works fine in 9.2.x.
On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Hi All,
>
>
>
> Has anyone been successful in offloading the database backup from the
> production database to the standby database?
>
>
>
> Kind Regards,
>
> Sabry
>
>
>
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
@ 2012-11-30 01:11 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Sabry Sadiq @ 2012-11-30 01:11 UTC (permalink / raw)
To: Lonni J Friedman <netllama@gmail.com>; +Cc: pgsql-admin
HI Lonni,
I am new to postgres.. How do I go about doing it? What are the gotchas?
Kind Regards,
Sabry
Sabry Sadiq
Systems Administrator
Whispir
Level 30 360 Collins Street
Melbourne / Victoria 3000 / Australia
GPO Box 130 / Victoria 3001 / Australia
T +61 3 8630 9900 / M +61 428 571 636
F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
1300 WHISPIR / 1300 944 774
www.whispir.com
This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
-----Original Message-----
From: Lonni J Friedman [mailto:netllama@gmail.com]
Sent: Friday, 30 November 2012 12:11 PM
To: Sabry Sadiq
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Backup
Yes. Works fine in 9.2.x.
On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Hi All,
>
>
>
> Has anyone been successful in offloading the database backup from the
> production database to the standby database?
>
>
>
> Kind Regards,
>
> Sabry
>
>
>
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
@ 2012-11-30 01:12 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
0 siblings, 1 reply; 52+ messages in thread
From: Lonni J Friedman @ 2012-11-30 01:12 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; +Cc: pgsql-admin
There aren't any, assuming that all of the servers are using the same
postgresql.conf. I'm referring to running pg_basebackup.
On Thu, Nov 29, 2012 at 5:11 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> HI Lonni,
>
> I am new to postgres.. How do I go about doing it? What are the gotchas?
>
> Kind Regards,
> Sabry
>
>
>
>
> Sabry Sadiq
> Systems Administrator
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:11 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> Yes. Works fine in 9.2.x.
>
> On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> Hi All,
>>
>>
>>
>> Has anyone been successful in offloading the database backup from the
>> production database to the standby database?
>>
>>
>>
>> Kind Regards,
>>
>> Sabry
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
@ 2012-11-30 01:13 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Sabry Sadiq @ 2012-11-30 01:13 UTC (permalink / raw)
To: Lonni J Friedman <netllama@gmail.com>; +Cc: pgsql-admin
Does it work well with version 9.1.3?
Sabry Sadiq
Systems Administrator
Whispir
Level 30 360 Collins Street
Melbourne / Victoria 3000 / Australia
GPO Box 130 / Victoria 3001 / Australia
T +61 3 8630 9900 / M +61 428 571 636
F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
1300 WHISPIR / 1300 944 774
www.whispir.com
This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
-----Original Message-----
From: Lonni J Friedman [mailto:netllama@gmail.com]
Sent: Friday, 30 November 2012 12:13 PM
To: Sabry Sadiq
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Backup
There aren't any, assuming that all of the servers are using the same postgresql.conf. I'm referring to running pg_basebackup.
On Thu, Nov 29, 2012 at 5:11 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> HI Lonni,
>
> I am new to postgres.. How do I go about doing it? What are the gotchas?
>
> Kind Regards,
> Sabry
>
>
>
>
> Sabry Sadiq
> Systems Administrator
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:11 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> Yes. Works fine in 9.2.x.
>
> On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> Hi All,
>>
>>
>>
>> Has anyone been successful in offloading the database backup from the
>> production database to the standby database?
>>
>>
>>
>> Kind Regards,
>>
>> Sabry
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
@ 2012-11-30 01:15 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:16 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
0 siblings, 1 reply; 52+ messages in thread
From: Lonni J Friedman @ 2012-11-30 01:15 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; +Cc: pgsql-admin
I don't know, I've never tried. If I had to guess, I'd say no, as
that version doesn't support cascading replication.
You never stated, how are you currently performing backups?
On Thu, Nov 29, 2012 at 5:13 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Does it work well with version 9.1.3?
>
>
>
> Sabry Sadiq
> Systems Administrator
>
> Whispir
> Level 30 360 Collins Street
> Melbourne / Victoria 3000 / Australia
> GPO Box 130 / Victoria 3001 / Australia
> T +61 3 8630 9900 / M +61 428 571 636
> F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
> 1300 WHISPIR / 1300 944 774
> www.whispir.com
>
>
>
>
> This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
>
>
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:13 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> There aren't any, assuming that all of the servers are using the same postgresql.conf. I'm referring to running pg_basebackup.
>
> On Thu, Nov 29, 2012 at 5:11 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> HI Lonni,
>>
>> I am new to postgres.. How do I go about doing it? What are the gotchas?
>>
>> Kind Regards,
>> Sabry
>>
>>
>>
>>
>> Sabry Sadiq
>> Systems Administrator
>> -----Original Message-----
>> From: Lonni J Friedman [mailto:netllama@gmail.com]
>> Sent: Friday, 30 November 2012 12:11 PM
>> To: Sabry Sadiq
>> Cc: pgsql-admin@postgresql.org
>> Subject: Re: [ADMIN] Backup
>>
>> Yes. Works fine in 9.2.x.
>>
>> On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>>> Hi All,
>>>
>>>
>>>
>>> Has anyone been successful in offloading the database backup from the
>>> production database to the standby database?
>>>
>>>
>>>
>>> Kind Regards,
>>>
>>> Sabry
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
@ 2012-11-30 01:16 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:17 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Sabry Sadiq @ 2012-11-30 01:16 UTC (permalink / raw)
To: Lonni J Friedman <netllama@gmail.com>; +Cc: pgsql-admin
Currently backups are performed on the master database and I want to offload that load to the standby
Sabry Sadiq
Systems Administrator
Whispir
Level 30 360 Collins Street
Melbourne / Victoria 3000 / Australia
GPO Box 130 / Victoria 3001 / Australia
T +61 3 8630 9900 / M +61 428 571 636
F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
1300 WHISPIR / 1300 944 774
www.whispir.com
-----Original Message-----
From: Lonni J Friedman [mailto:netllama@gmail.com]
Sent: Friday, 30 November 2012 12:15 PM
To: Sabry Sadiq
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Backup
I don't know, I've never tried. If I had to guess, I'd say no, as that version doesn't support cascading replication.
You never stated, how are you currently performing backups?
On Thu, Nov 29, 2012 at 5:13 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Does it work well with version 9.1.3?
>
>
>
> Sabry Sadiq
> Systems Administrator
>
> Whispir
> Level 30 360 Collins Street
> Melbourne / Victoria 3000 / Australia
> GPO Box 130 / Victoria 3001 / Australia T +61 3 8630 9900 / M +61 428
> 571 636 F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
> 1300 WHISPIR / 1300 944 774
> www.whispir.com
>
>
>
>
> This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
>
>
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:13 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> There aren't any, assuming that all of the servers are using the same postgresql.conf. I'm referring to running pg_basebackup.
>
> On Thu, Nov 29, 2012 at 5:11 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> HI Lonni,
>>
>> I am new to postgres.. How do I go about doing it? What are the gotchas?
>>
>> Kind Regards,
>> Sabry
>>
>>
>>
>>
>> Sabry Sadiq
>> Systems Administrator
>> -----Original Message-----
>> From: Lonni J Friedman [mailto:netllama@gmail.com]
>> Sent: Friday, 30 November 2012 12:11 PM
>> To: Sabry Sadiq
>> Cc: pgsql-admin@postgresql.org
>> Subject: Re: [ADMIN] Backup
>>
>> Yes. Works fine in 9.2.x.
>>
>> On Thu, Nov 29, 2012 at 4:59 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>>> Hi All,
>>>
>>>
>>>
>>> Has anyone been successful in offloading the database backup from
>>> the production database to the standby database?
>>>
>>>
>>>
>>> Kind Regards,
>>>
>>> Sabry
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:16 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
@ 2012-11-30 01:17 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:17 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
0 siblings, 1 reply; 52+ messages in thread
From: Lonni J Friedman @ 2012-11-30 01:17 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; +Cc: pgsql-admin
*how* are the backups being generated?
On Thu, Nov 29, 2012 at 5:16 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Currently backups are performed on the master database and I want to offload that load to the standby
>
>
>
> Sabry Sadiq
> Systems Administrator
>
> Whispir
> Level 30 360 Collins Street
> Melbourne / Victoria 3000 / Australia
> GPO Box 130 / Victoria 3001 / Australia
> T +61 3 8630 9900 / M +61 428 571 636
> F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
> 1300 WHISPIR / 1300 944 774
> www.whispir.com
>
>
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:15 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> I don't know, I've never tried. If I had to guess, I'd say no, as that version doesn't support cascading replication.
>
> You never stated, how are you currently performing backups?
>
> On Thu, Nov 29, 2012 at 5:13 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> Does it work well with version 9.1.3?
>>
>>
>>
>> Sabry Sadiq
>> Systems Administrator
>>
>> Whispir
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:16 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:17 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
@ 2012-11-30 01:17 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 21:25 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
0 siblings, 1 reply; 52+ messages in thread
From: Sabry Sadiq @ 2012-11-30 01:17 UTC (permalink / raw)
To: Lonni J Friedman <netllama@gmail.com>; +Cc: pgsql-admin
Pg_dump
Sabry Sadiq
Systems Administrator
Whispir
Level 30 360 Collins Street
Melbourne / Victoria 3000 / Australia
GPO Box 130 / Victoria 3001 / Australia
T +61 3 8630 9900 / M +61 428 571 636
F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
1300 WHISPIR / 1300 944 774
www.whispir.com
This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
-----Original Message-----
From: Lonni J Friedman [mailto:netllama@gmail.com]
Sent: Friday, 30 November 2012 12:17 PM
To: Sabry Sadiq
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Backup
*how* are the backups being generated?
On Thu, Nov 29, 2012 at 5:16 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Currently backups are performed on the master database and I want to
> offload that load to the standby
>
>
>
> Sabry Sadiq
> Systems Administrator
>
> Whispir
> Level 30 360 Collins Street
> Melbourne / Victoria 3000 / Australia
> GPO Box 130 / Victoria 3001 / Australia T +61 3 8630 9900 / M +61 428
> 571 636 F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
> 1300 WHISPIR / 1300 944 774
> www.whispir.com
>
>
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:15 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> I don't know, I've never tried. If I had to guess, I'd say no, as that version doesn't support cascading replication.
>
> You never stated, how are you currently performing backups?
>
> On Thu, Nov 29, 2012 at 5:13 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> Does it work well with version 9.1.3?
>>
>>
>>
>> Sabry Sadiq
>> Systems Administrator
>>
>> Whispir
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:16 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:17 ` Re: Backup Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:17 ` Re: Backup Sabry Sadiq <ssadiq@whispir.com>
@ 2012-11-30 21:25 ` Lonni J Friedman <netllama@gmail.com>
0 siblings, 0 replies; 52+ messages in thread
From: Lonni J Friedman @ 2012-11-30 21:25 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; +Cc: pgsql-admin
I can generate a backup using pg_dump on a slave with 9.2.1. No clue
if it works with 9.1.x (or older) versions though.
On Thu, Nov 29, 2012 at 5:17 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
> Pg_dump
>
>
>
> Sabry Sadiq
> Systems Administrator
>
> Whispir
> Level 30 360 Collins Street
> Melbourne / Victoria 3000 / Australia
> GPO Box 130 / Victoria 3001 / Australia
> T +61 3 8630 9900 / M +61 428 571 636
> F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
> 1300 WHISPIR / 1300 944 774
> www.whispir.com
>
>
>
>
> This communication contains information which is confidential and the copyright of Whispir or a third party. If you have received this email in error please notify us by return email or telephone Whispir on 1300 WHISPIR (1300 9447747) or +613 8630 9900 and delete the document and delete all copies immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Whispir. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of Whispir. Except as required at law, Whispir does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
>
>
> -----Original Message-----
> From: Lonni J Friedman [mailto:netllama@gmail.com]
> Sent: Friday, 30 November 2012 12:17 PM
> To: Sabry Sadiq
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Backup
>
> *how* are the backups being generated?
>
> On Thu, Nov 29, 2012 at 5:16 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>> Currently backups are performed on the master database and I want to
>> offload that load to the standby
>>
>>
>>
>> Sabry Sadiq
>> Systems Administrator
>>
>> Whispir
>> Level 30 360 Collins Street
>> Melbourne / Victoria 3000 / Australia
>> GPO Box 130 / Victoria 3001 / Australia T +61 3 8630 9900 / M +61 428
>> 571 636 F +61 3 8630 9990 / E mailto:ssadiq@whispir.com
>> 1300 WHISPIR / 1300 944 774
>> www.whispir.com
>>
>>
>> -----Original Message-----
>> From: Lonni J Friedman [mailto:netllama@gmail.com]
>> Sent: Friday, 30 November 2012 12:15 PM
>> To: Sabry Sadiq
>> Cc: pgsql-admin@postgresql.org
>> Subject: Re: [ADMIN] Backup
>>
>> I don't know, I've never tried. If I had to guess, I'd say no, as that version doesn't support cascading replication.
>>
>> You never stated, how are you currently performing backups?
>>
>> On Thu, Nov 29, 2012 at 5:13 PM, Sabry Sadiq <ssadiq@whispir.com> wrote:
>>> Does it work well with version 9.1.3?
>>>
>>>
>>>
>>> Sabry Sadiq
>>> Systems Administrator
>>>
>>> Whispir
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
* Re: Backup
@ 2012-11-30 01:28 Kevin Grittner <kgrittn@mail.com>
0 siblings, 0 replies; 52+ messages in thread
From: Kevin Grittner @ 2012-11-30 01:28 UTC (permalink / raw)
To: Sabry Sadiq <ssadiq@whispir.com>; Lonni J Friedman <netllama@gmail.com>; +Cc: pgsql-admin
Sabry Sadiq wrote:
> Does it work well with version 9.1.3?
It might work better in 9.1.6:
http://www.postgresql.org/support/versioning/
And it would probably pay to keep up-to-date as new minor releases
become available.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 52+ messages in thread
end of thread, other threads:[~2012-11-30 21:25 UTC | newest]
Thread overview: 52+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-07-23 12:24 Backup Eduardo S. Fontanetti <dufuzzy@yahoo.com.br>
2004-07-24 03:23 ` mike g <mike@thegodshalls.com>
2005-01-05 05:45 backup Jimmy P Mani <jimmymani@gmail.com>
2005-01-08 22:20 ` Re: backup Jyry Kuukkanen <jyry@neutech.fi>
2005-01-08 22:22 ` Re: backup Michael Fuhr <mike@fuhr.org>
2005-03-23 20:41 Backup Joseph M. Day <jday@gisolutions.us>
2005-03-23 21:13 ` Joshua D. Drake <jd@commandprompt.com>
2005-03-23 22:37 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-03-23 21:01 Re: Backup Joseph M. Day <jday@gisolutions.us>
2005-03-23 21:20 ` Jay A. Kreibich <jak@uiuc.edu>
2005-03-23 21:15 Re: Backup Jason Minion <jason.minion@sigler.com>
2005-03-25 13:30 Re: Backup John Jensen <jrj@ft.fo>
2005-12-15 01:00 backup Muhammad Farid <farid13@gmail.com>
2005-12-15 13:37 ` Re: backup Devrim GUNDUZ <devrim@commandprompt.com>
2005-12-15 16:52 ` Re: backup Dianne Yumul <dianne@wellsgaming.com>
2006-12-13 04:43 Backup Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 07:39 ` Shoaib Mir <shoaibmir@gmail.com>
2006-12-13 10:51 ` Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 11:21 ` Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
2006-12-14 10:28 ` Eduardo J. Ortega <ejortegau@cable.net.co>
2006-12-13 11:22 ` Shoaib Mir <shoaibmir@gmail.com>
2008-01-24 19:08 Backup Dominic Carlucci <carlucci@cae.com>
2008-01-25 00:34 ` Phillip Smith <phillip.smith@weatherbeeta.com.au>
2008-01-25 09:21 ` Simon Riggs <simon@2ndquadrant.com>
2008-01-31 12:21 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 13:28 ` Simon Riggs <simon@2ndquadrant.com>
2008-01-31 14:34 ` Martijn van Oosterhout <kleptog@svana.org>
2008-01-31 14:43 ` Magnus Hagander <magnus@hagander.net>
2008-01-31 15:02 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 15:58 ` Simon Riggs <simon@2ndquadrant.com>
2008-02-06 13:29 ` Hannes Dorbath <light@theendofthetunnel.de>
2008-02-06 13:49 ` Hannes Dorbath <light@theendofthetunnel.de>
2008-01-31 15:00 ` Chander Ganesan <chander@otg-nc.com>
2008-01-31 15:09 ` Alvaro Herrera <alvherre@commandprompt.com>
2008-01-31 15:48 ` Simon Riggs <simon@2ndquadrant.com>
2008-01-25 00:47 ` Scott Marlowe <scott.marlowe@gmail.com>
2008-01-30 04:15 ` Vishal Arora <aroravishal22@hotmail.com>
2008-01-30 04:27 ` Guido Barosio <gbarosio@gmail.com>
2012-06-18 17:50 backup lohita nama <namalohita@gmail.com>
2012-06-18 17:57 ` Re: backup Kevin Grittner <Kevin.Grittner@wicourts.gov>
2012-06-18 17:59 ` Re: backup Frederiko Costa <frederiko@gmail.com>
2012-11-30 00:59 Backup Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:10 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:11 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:12 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:13 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:15 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:16 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 01:17 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:17 ` Sabry Sadiq <ssadiq@whispir.com>
2012-11-30 21:25 ` Lonni J Friedman <netllama@gmail.com>
2012-11-30 01:28 Re: Backup Kevin Grittner <kgrittn@mail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox