Re: Amanda and PostgreSQL
Using rsync: shutdown db rsync all data to backup disk/raid/machine start db amanda backup the backup disk/raid/machine The first run of rsync will be the slowest - must send all data to make a complete copy. The next run of rsync will be much faster. rsync only sends new or changed data. So if 3 bytes in a 1G file are changed, only the changed 3 bytes are sent. Plus you have the lastest backup copy in an easily retrieved format. Your rsync speed will depend on the size of the db the amount of daily changes. This is how I backup an Oracle application using amanda. - toby bluhm it support, development systems philips medical systems, cleveland ohio [EMAIL PROTECTED] 440-483-5323 Celeron: Derived from the latin word, 'celer', meaning 'fast' or 'swift', as in 'celery' - the fastest of all vegetables.
Re: Amanda and PostgreSQL
On Thu, 13 Jan 2005 [EMAIL PROTECTED] wrote:
Using rsync:
shutdown db
rsync all data to backup disk/raid/machine
start db
amanda backup the backup disk/raid/machine
The first run of rsync will be the slowest - must send all data to make a
complete copy. The next run of rsync will be much faster. rsync only sends
new or changed data. So if 3 bytes in a 1G file are changed, only the
changed 3 bytes are sent. Plus you have the lastest backup copy in an
Hmm, not exactly true ;-) Rsync operates on blocks.
easily retrieved format. Your rsync speed will depend on the size of the
db the amount of daily changes.
And make sure to use `rsync -za --delete'. You can drop the `-z' if you don't
want to use compression (for slow CPUs and very fast networks).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Amanda and PostgreSQL
Title: Amanda and PostgreSQL Hi! I have Amanda server running on a Linux box. In another machine, I have Solaris 9 running Amanda client and PostgreSQL. I would like to know if someone has experience backupping PostgreSQL with Amanda. I have thought the following solutions: 1. Making a file system level backup. The problem is that I'll have to stop the PostgreSQL engine first, so the DB will be unoperative for a while. 2. To use pg_dump to get a hot snapshot of the desired DB, put it on some directory and then backup that directory with amanda. I saw somewhere a kind of script that interacts between Oracle and Amanda, and it is possible to backup the desired DB without stopping the engine. Is there something like that for postgreSQL?? Any idea?? Bests Regards Germán C. Basisty EIP Sistemas Consultor - Tecnología informática Paso 158 (Q8340FTG) Zapala, Pcia. de Neuquén Argentina tel. +54 (02942) 422 336 fax +54 (02942) 422 336 [EMAIL PROTECTED] HYPERLINK http://www.eipsistemas.ath.cxhttp://www.eipsistemas.ath.cx -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005
Re: Amanda and PostgreSQL
On Wed, 12 Jan 2005, [iso-8859-1] Germán C. Basisty wrote: 2. To use pg_dump to get a hot snapshot of the desired DB, put it on some directory and then backup that directory with amanda. We use pg_dump. We just run it from cron in advance of amanda's start time. -Mitch
Re: Amanda and PostgreSQL
This one time, at band camp, Germán C. Basisty wrote: Hi! I have Amanda server running on a Linux box. In another machine, I have Solaris 9 running Amanda client and PostgreSQL. I would like to know if someone has experience backupping PostgreSQL with Amanda. I have thought the following solutions: 1. Making a file system level backup. The problem is that I'll have to stop the PostgreSQL engine first, so the DB will be unoperative for a while. 2. To use pg_dump to get a hot snapshot of the desired DB, put it on some directory and then backup that directory with amanda. I do this, and cross my fingers that the pg_dumpall is done before the amanda run. I saw somewhere a kind of script that interacts between Oracle and Amanda, and it is possible to backup the desired DB without stopping the engine. Is there something like that for postgreSQL?? So I had a crazy idea that hasn't yet been implemented, a pg dumper similar in appearance to GNUTAR and DUMP on the client machine. Your DLE would look somethign like: host database/table pg where pg would be the dumptype telling amanda to use the pg dumper. The net effect is that you'd get a hot snapshot written straight to amanda, so you wouldn't have to worry about scheduling the dumps of each at the right time. If someone wants to beat me to the implementation though, please go right ahead :-)
Re: Amanda and PostgreSQL
On Thu, 13 Jan 2005, Jamie Wilkinson wrote: So I had a crazy idea that hasn't yet been implemented, a pg dumper similar in appearance to GNUTAR and DUMP on the client machine. Your DLE would look somethign like: host database/table pg where pg would be the dumptype telling amanda to use the pg dumper. The net effect is that you'd get a hot snapshot written straight to amanda, so you wouldn't have to worry about scheduling the dumps of each at the right time. If someone wants to beat me to the implementation though, please go right ahead :-) What you want is something called DUMPER-API. Unfortunately it doesn't actually exist. It's documented but still waiting for someone to code it. In the mean time, the standard workaround is to use the framework here: ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.* This is a wrapper script that will pretend to be gnutar to amanda, but run whatever you tell it to instead on the client. -Mitch
Re: Amanda and PostgreSQL
On Wednesday 12 January 2005 20:57, Jamie Wilkinson wrote: This one time, at band camp, Germán C. Basisty wrote: Hi! I have Amanda server running on a Linux box. In another machine, I have Solaris 9 running Amanda client and PostgreSQL. I would like to know if someone has experience backupping PostgreSQL with Amanda. I have thought the following solutions: 1. Making a file system level backup. The problem is that I'll have to stop the PostgreSQL engine first, so the DB will be unoperative for a while. 2. To use pg_dump to get a hot snapshot of the desired DB, put it on some directory and then backup that directory with amanda. I do this, and cross my fingers that the pg_dumpall is done before the amanda run. I saw somewhere a kind of script that interacts between Oracle and Amanda, and it is possible to backup the desired DB without stopping the engine. Is there something like that for postgreSQL?? So I had a crazy idea that hasn't yet been implemented, a pg dumper similar in appearance to GNUTAR and DUMP on the client machine. Your DLE would look somethign like: host database/table pg where pg would be the dumptype telling amanda to use the pg dumper. The net effect is that you'd get a hot snapshot written straight to amanda, so you wouldn't have to worry about scheduling the dumps of each at the right time. If someone wants to beat me to the implementation though, please go right ahead :-) I've no idea why it cannot be scripted, such that amdump is started when pg_dump is done and the shell returns to the next line of the script. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.31% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Amanda and PostgreSQL
This one time, at band camp, Gene Heskett wrote: On Wednesday 12 January 2005 20:57, Jamie Wilkinson wrote: This one time, at band camp, Germán C. Basisty wrote: Hi! I have Amanda server running on a Linux box. In another machine, I have Solaris 9 running Amanda client and PostgreSQL. I would like to know if someone has experience backupping PostgreSQL with Amanda. I have thought the following solutions: 1. Making a file system level backup. The problem is that I'll have to stop the PostgreSQL engine first, so the DB will be unoperative for a while. 2. To use pg_dump to get a hot snapshot of the desired DB, put it on some directory and then backup that directory with amanda. I do this, and cross my fingers that the pg_dumpall is done before the amanda run. I saw somewhere a kind of script that interacts between Oracle and Amanda, and it is possible to backup the desired DB without stopping the engine. Is there something like that for postgreSQL?? So I had a crazy idea that hasn't yet been implemented, a pg dumper similar in appearance to GNUTAR and DUMP on the client machine. Your DLE would look somethign like: host database/table pg where pg would be the dumptype telling amanda to use the pg dumper. The net effect is that you'd get a hot snapshot written straight to amanda, so you wouldn't have to worry about scheduling the dumps of each at the right time. If someone wants to beat me to the implementation though, please go right ahead :-) I've no idea why it cannot be scripted, such that amdump is started when pg_dump is done and the shell returns to the next line of the script. Because the database being dumped is not on the machine that runs amdump, and adding another RPC that duplicates the one already in amanda is unjustifiable.
Re: Amanda and PostgreSQL
On Thu, Jan 13, 2005 at 03:09:42PM +1100, Jamie Wilkinson wrote: Because the database being dumped is not on the machine that runs amdump, and adding another RPC that duplicates the one already in amanda is unjustifiable. It would be a bit of a hack, but if you're already writing a shell script you could use some kind of passworldess SSH system (public keys or otherwise) that would login to the amdump machine and do a dump of the database. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- http://www.cs.earlham.edu/~skylar/ pgp0RdooWPPld.pgp Description: PGP signature
Re: Amanda and PostgreSQL
This one time, at band camp, Skylar Thompson wrote: On Thu, Jan 13, 2005 at 03:09:42PM +1100, Jamie Wilkinson wrote: Because the database being dumped is not on the machine that runs amdump, and adding another RPC that duplicates the one already in amanda is unjustifiable. It would be a bit of a hack, but if you're already writing a shell script you could use some kind of passworldess SSH system (public keys or otherwise) that would login to the amdump machine and do a dump of the database. Yes. Currently, we have somethign that works good enough. If I wanted to make it better, I'd do it right rather than add another hack, I think that would be a much better investment of time. But thanks for your advice.
