From: John R. Allgood <john@turbocorp.com>
To: Kenneth Marshall <ktm@is.rice.edu>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres Backup Questions
Date: Thu, 01 Jun 2006 14:20:19 -0400
Message-ID: <447F2FE3.30402@turbocorp.com> (raw)
In-Reply-To: <20060601180115.GH15172@it.is.rice.edu>
References: <447F049E.2000408@turbocorp.com>
<1149179444.25526.139.camel@state.g2switchworks.com>
<447F2A73.3080104@turbocorp.com>
<20060601180115.GH15172@it.is.rice.edu>
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."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: john@turbocorp.com, ktm@is.rice.edu, smarlowe@g2switchworks.com
Subject: Re: Postgres Backup Questions
In-Reply-To: <447F2FE3.30402@turbocorp.com>
References: <447F049E.2000408@turbocorp.com> <1149179444.25526.139.camel@state.g2switchworks.com> <447F2A73.3080104@turbocorp.com> <20060601180115.GH15172@it.is.rice.edu> <447F2FE3.30402@turbocorp.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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