pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgres Backup Questions
5+ messages / 3 participants
[nested] [flat]
* Postgres Backup Questions
@ 2006-06-01 15:15 John R. Allgood <john@turbocorp.com>
0 siblings, 1 reply; 5+ messages in thread
From: John R. Allgood @ 2006-06-01 15:15 UTC (permalink / raw)
To: pgsql-admin
Hello
I have a question regarding backups on Postgresql 7.4.7-2. We are
currently using a Progress database and will be moving over to Postgres
this month. In Progress there is a way to verify your backups does
Postgres have anything similiar or is there other ways to accompplish
this. I am currently writing backup and other utility scripts and would
like to incorporate this into my program.
Thanks
John Allgood -ESC
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Backup Questions
@ 2006-06-01 16:30 Scott Marlowe <smarlowe@g2switchworks.com>
parent: John R. Allgood <john@turbocorp.com>
0 siblings, 1 reply; 5+ messages in thread
From: Scott Marlowe @ 2006-06-01 16:30 UTC (permalink / raw)
To: John R. Allgood <john@turbocorp.com>; +Cc: pgsql-admin
On Thu, 2006-06-01 at 10:15, John R. Allgood wrote:
> Hello
>
> I have a question regarding backups on Postgresql 7.4.7-2. We are
> currently using a Progress database and will be moving over to Postgres
> this month. In Progress there is a way to verify your backups does
> Postgres have anything similiar or is there other ways to accompplish
> this. I am currently writing backup and other utility scripts and would
> like to incorporate this into my program.
I wrapped my backup in a bash script, and that seems to catch errors.
something like:
if !(
/data01/pg/bin/pg_dump dbname > dbname.sql
);
then
cat "backup failed"|mail -s "backup failed" yourname@yourdomain.com;
fi
To test this, I corrupted a table in a test database to force a hard
failure, and it sent an email. Don't know if it's a comprehensive test,
but it seems to work for us.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Backup Questions
@ 2006-06-01 17:57 John R. Allgood <john@turbocorp.com>
parent: Scott Marlowe <smarlowe@g2switchworks.com>
0 siblings, 1 reply; 5+ messages in thread
From: John R. Allgood @ 2006-06-01 17:57 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: pgsql-admin
Hey Again
Thanks for the input. but what I am wanting to check for is CRC
errors and block errors. The backups are written to tape and I would
like a way to verify the data on the tape as compared to the data on the
server. I may be way off here but I just want to be sure I am getting
reliable backups.
Thanks
Scott Marlowe wrote:
> On Thu, 2006-06-01 at 10:15, John R. Allgood wrote:
>
>> Hello
>>
>> I have a question regarding backups on Postgresql 7.4.7-2. We are
>> currently using a Progress database and will be moving over to Postgres
>> this month. In Progress there is a way to verify your backups does
>> Postgres have anything similiar or is there other ways to accompplish
>> this. I am currently writing backup and other utility scripts and would
>> like to incorporate this into my program.
>>
>
> I wrapped my backup in a bash script, and that seems to catch errors.
> something like:
>
> if !(
> /data01/pg/bin/pg_dump dbname > dbname.sql
> );
> then
> cat "backup failed"|mail -s "backup failed" yourname@yourdomain.com;
> fi
>
> To test this, I corrupted a table in a test database to force a hard
> failure, and it sent an email. Don't know if it's a comprehensive test,
> but it seems to work for us.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
All I can think of is a platter of organic PRUNE CRISPS being trampled
by an army of swarthy, Italian LOUNGE SINGERS ...
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Backup Questions
@ 2006-06-01 18:01 Kenneth Marshall <ktm@it.is.rice.edu>
parent: John R. Allgood <john@turbocorp.com>
0 siblings, 1 reply; 5+ messages in thread
From: Kenneth Marshall @ 2006-06-01 18:01 UTC (permalink / raw)
To: John R. Allgood <john@turbocorp.com>; +Cc: Scott Marlowe <smarlowe@g2switchworks.com>; pgsql-admin
John,
We accomplished this using an inline filter to capture the
checksum and size for the entire dump to tape. Then we re-read
the tape to see if the tape generated the same checksum and size.
That is probably about a good as you are going to get.
Ken
On Thu, Jun 01, 2006 at 01:57:07PM -0400, John R. Allgood wrote:
> Hey Again
>
> Thanks for the input. but what I am wanting to check for is CRC
> errors and block errors. The backups are written to tape and I would
> like a way to verify the data on the tape as compared to the data on the
> server. I may be way off here but I just want to be sure I am getting
> reliable backups.
>
> Thanks
>
> Scott Marlowe wrote:
> >On Thu, 2006-06-01 at 10:15, John R. Allgood wrote:
> >
> >>Hello
> >>
> >> I have a question regarding backups on Postgresql 7.4.7-2. We are
> >>currently using a Progress database and will be moving over to Postgres
> >>this month. In Progress there is a way to verify your backups does
> >>Postgres have anything similiar or is there other ways to accompplish
> >>this. I am currently writing backup and other utility scripts and would
> >>like to incorporate this into my program.
> >>
> >
> >I wrapped my backup in a bash script, and that seems to catch errors.
> >something like:
> >
> >if !(
> > /data01/pg/bin/pg_dump dbname > dbname.sql
> > );
> >then
> > cat "backup failed"|mail -s "backup failed" yourname@yourdomain.com;
> >fi
> >
> >To test this, I corrupted a table in a test database to force a hard
> >failure, and it sent an email. Don't know if it's a comprehensive test,
> >but it seems to work for us.
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 1: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
> >
>
> --
> All I can think of is a platter of organic PRUNE CRISPS being trampled
> by an army of swarthy, Italian LOUNGE SINGERS ...
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Backup Questions
@ 2006-06-01 18:20 John R. Allgood <john@turbocorp.com>
parent: Kenneth Marshall <ktm@it.is.rice.edu>
0 siblings, 0 replies; 5+ messages in thread
From: John R. Allgood @ 2006-06-01 18:20 UTC (permalink / raw)
To: Kenneth Marshall <ktm@is.rice.edu>; +Cc: Scott Marlowe <smarlowe@g2switchworks.com>; pgsql-admin
Hey
That sounds like what I would need to do. Could you provide a few
more details about how this was accomplished.
Thanks
John Allgood - ESC
Kenneth Marshall wrote:
> John,
>
> We accomplished this using an inline filter to capture the
> checksum and size for the entire dump to tape. Then we re-read
> the tape to see if the tape generated the same checksum and size.
> That is probably about a good as you are going to get.
>
> Ken
>
> On Thu, Jun 01, 2006 at 01:57:07PM -0400, John R. Allgood wrote:
>
>> Hey Again
>>
>> Thanks for the input. but what I am wanting to check for is CRC
>> errors and block errors. The backups are written to tape and I would
>> like a way to verify the data on the tape as compared to the data on the
>> server. I may be way off here but I just want to be sure I am getting
>> reliable backups.
>>
>> Thanks
>>
>> Scott Marlowe wrote:
>>
>>> On Thu, 2006-06-01 at 10:15, John R. Allgood wrote:
>>>
>>>
>>>> Hello
>>>>
>>>> I have a question regarding backups on Postgresql 7.4.7-2. We are
>>>> currently using a Progress database and will be moving over to Postgres
>>>> this month. In Progress there is a way to verify your backups does
>>>> Postgres have anything similiar or is there other ways to accompplish
>>>> this. I am currently writing backup and other utility scripts and would
>>>> like to incorporate this into my program.
>>>>
>>>>
>>> I wrapped my backup in a bash script, and that seems to catch errors.
>>> something like:
>>>
>>> if !(
>>> /data01/pg/bin/pg_dump dbname > dbname.sql
>>> );
>>> then
>>> cat "backup failed"|mail -s "backup failed" yourname@yourdomain.com;
>>> fi
>>>
>>> To test this, I corrupted a table in a test database to force a hard
>>> failure, and it sent an email. Don't know if it's a comprehensive test,
>>> but it seems to work for us.
>>>
>>> ---------------------------(end of broadcast)---------------------------
>>> TIP 1: if posting/reading through Usenet, please send an appropriate
>>> subscribe-nomail command to majordomo@postgresql.org so that your
>>> message can get through to the mailing list cleanly
>>>
>>>
>> --
>> All I can think of is a platter of organic PRUNE CRISPS being trampled
>> by an army of swarthy, Italian LOUNGE SINGERS ...
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 5: don't forget to increase your free space map settings
>>
>>
--
"I thought you were trying to get into shape."
"I am. The shape I've selected is a triangle."
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2006-06-01 18:20 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-06-01 15:15 Postgres Backup Questions John R. Allgood <john@turbocorp.com>
2006-06-01 16:30 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-06-01 17:57 ` John R. Allgood <john@turbocorp.com>
2006-06-01 18:01 ` Kenneth Marshall <ktm@it.is.rice.edu>
2006-06-01 18:20 ` John R. Allgood <john@turbocorp.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