Hi List,
please find below a
1. A script that takes remote base backups of a postgresql database.
it assumes a password less communication between the backup
server and the database server. After taking a base backup it removes
that un neccesary WAL log files from the archive folder. The script
On 4/13/06, Grega Bremec <[EMAIL PROTECTED]> wrote:> -BEGIN PGP SIGNED MESSAGE-> Hash: RIPEMD160> > Rajesh Kumar Mallah wrote:> > Is cluttering of the wal archive area in cases where that backup
> > had to be re-started for whatever reasons is the *only* concern ?> > Well, yes, to be honest
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
> Is cluttering of the wal archive area in cases where that backup
> had to be re-started for whatever reasons is the *only* concern ?
Well, yes, to be honest. But it may in consequence cause problems of
another kind, w
n the proper LVM disk group for the snapshot
> volume.
>
> Greg
>
>
>
> From: [EMAIL PROTECTED] on behalf of Tom Lane
> Sent: Mon 4/10/2006 7:19 PM
> To: Bruce Momjian
> Cc: [EMAIL PROTECTED]; 'Rajesh Kumar Mallah'; pgsq
Hi,
On Tue, 11 Apr 2006, Spiegelberg, Greg wrote:
You should implement filesystem or volume level snapshots. LVM,
Veritas and the like all have the functionality and it gets the
database out of "backup" mode quickly.
from what I understand there is no need to keep the time between
pg_start_ba
Title: Re: FW: [ADMIN] Setting up of PITR system.
You should implement
filesystem or volume level snapshots. LVM, Veritas and the like all have
the functionality and it gets the database out of "backup" mode
quickly.
http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.htm
Bruce Momjian writes:
> Tom Lane wrote:
>> It definitely is a pain in the neck that GNU tar complains about files
>> changing underneath it --- I've looked for a way to disable that, or at
>> least reduce it to a warning instead of an error condition, but gtar
>> doesn't seem to have such a switch
Tom Lane wrote:
> It definitely is a pain in the neck that GNU tar complains about files
> changing underneath it --- I've looked for a way to disable that, or at
> least reduce it to a warning instead of an error condition, but gtar
> doesn't seem to have such a switch. You should try alternative
> Rajesh Kumar Mallah wrote:
> |>| Do you see any problem in the current approach ?
> |>| i have seen it working fine till now.
> |>
> |>I do, to be honest. The WAL location counter accounts for 4294967295
> |>positions and while I'm certain that's WAY more than the average number
> |>of transacti
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
|>| Do you see any problem in the current approach ?
|>| i have seen it working fine till now.
|>
|>I do, to be honest. The WAL location counter accounts for 4294967295
|>positions and while I'm certain that's WAY more
> | Do you see any problem in the current approach ?
> | i have seen it working fine till now.
>
> I do, to be honest. The WAL location counter accounts for 4294967295
> positions and while I'm certain that's WAY more than the average number
> of transactions that go into a WAL, quite a number of
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
| it takes a while (i dont know how much) for the .backup file to get
| archived and appear in the wal archive area. thats why i prefer to
| use the wal log filename (0001000A0068) instead of
| something lik
On 4/3/06, Brendan Duddridge <[EMAIL PROTECTED]> wrote:
> Whenever you get a finalized script including all the enhancements
> you've been talking about,
> I would really love to have a copy as I'm sure lots of people here
> would. I think this is
> something that should be included in the standard
Whenever you get a finalized script including all the enhancements
you've been talking about,
I would really love to have a copy as I'm sure lots of people here
would. I think this is
something that should be included in the standard distribution.
Can I make a couple of suggestions?
1. Inclu
Rajesh Kumar Mallah wrote:
> Another area i was thinking to improve this script was to
> make it dig out all the tablespace folders to be archived by looking
> into PGDATADIR/pg_tblspc . This shall make the script more generic.
>
> pg_tblspc as contents like below:
>
> $ ls -l
> total 0
> lrwxr
On 4/2/06, Grega Bremec <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Rajesh Kumar Mallah wrote:
> |
> | Instead of taking a round about method i am using the content of the
> | file, (This was also suggested by Andy at somepoint)
>
> After reading the docs a
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
|
| Instead of taking a round about method i am using the content of the
| file, (This was also suggested by Andy at somepoint)
After reading the docs again, that's what I would do as well, indeed. :)
| lately i feel
On 4/1/06, Grega Bremec <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Rajesh Kumar Mallah wrote:
> | Dear Grega ,
> |
> | Thanks for the useful tips and error spotting,
> | i am incorporating some of them and testing
> | the script in my server . I have conce
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Grega Bremec wrote:
| ~ find ${WAL_ARCHIVE} -type f | sort -g | while read archive; do
| ~if [ ! "${archive}" = "${REF_FILE}" ]; then
Actually, this test is only possible since ${REF_FILE} was expanded
using the ${WAL_FILE} mask and will co
06 7:19 pm
To: Jim C. Nasby; Tom Lane
Cc: [EMAIL PROTECTED]; Rajesh Kumar Mallah;
pgsql-admin@postgresql.org
Subject: Re: FW: [ADMIN] Setting up of PITR system.
We have high volume inserts happening with wal files being generated
very rapidly. Will the fact that the files change as the tar happen
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
| Dear Grega ,
|
| Thanks for the useful tips and error spotting,
| i am incorporating some of them and testing
| the script in my server . I have concerns regarding
| some of your optimisations that makes the script le
To: Tom Lane
> Cc: [EMAIL PROTECTED]; 'Rajesh Kumar Mallah';
> pgsql-admin@postgresql.org
> Subject: Re: FW: [ADMIN] Setting up of PITR system.
>
> On Wed, Mar 29, 2006 at 09:46:30AM -0500, Tom Lane wrote:
> > It definitely is a pain in the neck that GNU tar complains
On 3/30/06, Grega Bremec <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Rajesh Kumar Mallah wrote:
> |
> | OK i am posting my full script [ its not heavy programming i guess :) ]
> | shall be grateful if you/someone could review it . (its well
> commented i t
:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
Sent: Friday, March 31, 2006 10:11 AM
To: Tom Lane
Cc: [EMAIL PROTECTED]; 'Rajesh Kumar Mallah';
pgsql-admin@postgresql.org
Subject: Re: FW: [ADMIN] Setting up of PITR system.
On Wed, Mar 29, 2006 at 09:46:30AM -0500, Tom Lane wrote:
> It de
On Wed, Mar 29, 2006 at 09:46:30AM -0500, Tom Lane wrote:
> It definitely is a pain in the neck that GNU tar complains about files
> changing underneath it --- I've looked for a way to disable that, or at
> least reduce it to a warning instead of an error condition, but gtar
> doesn't seem to have
On Wed, Mar 29, 2006 at 06:15:59PM +0530, Rajesh Kumar Mallah wrote:
> > Also you wouldn't particular need any heavy programming ? I'm sure a simple
> > shell script could be written in bash to pick out the correct files.
>
> OK i am posting my full script [ its not heavy programming i guess :) ]
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
|
| OK i am posting my full script [ its not heavy programming i guess :) ]
| shall be grateful if you/someone could review it . (its well
commented i think)
| script also carries sample data.
|
| it does following
| 1
"Andy Shellam" <[EMAIL PROTECTED]> writes:
> If pg_start_backup is used correctly, no data pages will be written to disk
> until pg_stop_backup is called, so this shouldn't be an issue
That's incorrect, the database will continue to operate normally. The
only thing pg_start_backup really does is
;>>>>
I used rsync like many others , it seems to work fine for me.
Regds
mallah.
>
> Andy
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Kumar Mallah
> Sent: Tuesday, 28 March, 2006 5:27 PM
> To: Tom Lan
On 3/28/06, Andy Shellam <[EMAIL PROTECTED]> wrote:
>
>
>
> we want to remove archived WAL log files which are no longer needed
> so that the size of wal_archive folder is under control.
>
> The DOCs say that filenames numerically less than the WAL record that
> pg_stop_backup()
> suggests can b
Cc: [EMAIL PROTECTED]; pgsql-admin@postgresql.org
Subject: Re: FW: [ADMIN] Setting up of PITR system.
---
secondly , i was asking about the tool for copying the
database directory not the one for archiving the logs.
when i use tar , it gives warning that the file changed
while it was reading the file
Hi,
Thanks everyone for the reply,
is it reasonable/advisable to start with the output of
pg_stop_backup() in a shell script to find the WAL
file being discussed, ie the FILE which can be used
as a reference for removing the older files ?
secondly , i was asking about the tool for copying the
da
"Andy Shellam" <[EMAIL PROTECTED]> writes:
> The DOCs say that filenames numerically less than the WAL record that
> pg_stop_backup() suggests can be removed. Will an alphabetical sorting
> be different from numerically sorted filename ?
If you're worried about that, try "LANG=C ls ..." to make su
we want to remove
archived WAL log files which are no longer needed
so that the size of wal_archive folder is under control.
The DOCs say that filenames numerically less than the WAL record that
pg_stop_backup()
suggests can be removed. Will an alphabetical sorting be different from
numeri
Hi,
Sorry last posting was accidently sent , incomplete,plese ignore.
We are trying to setup PITR system based on documentation
http://www.postgresql.org/docs/8.1/interactive/backup-online.html
We have 3 questions regarding
1. Selection of archived WAL records that can be safely removed.
2. Kno
Hi,
We are trying to setup PITR system based on documentation
http://www.postgresql.org/docs/8.1/interactive/backup-online.html
We have 3 questions regarding
1. Selection of archived WAL records that can be safely removed.
2. Knowing the relevant WAL record just after pg_stop_backup()
3. Recomme
36 matches
Mail list logo
