X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 4D8149FA040 for ; Thu, 1 Jun 2006 14:57:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 41470-06 for ; Thu, 1 Jun 2006 14:57:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from Mercury.turbocorp.com (mercury.turbocorp.com [198.212.166.40]) by postgresql.org (Postfix) with ESMTP id 783129FA5C8 for ; Thu, 1 Jun 2006 14:57:08 -0300 (ADT) Received: from [198.212.166.61] (Voyager.turbocorp.com [198.212.166.61]) by Mercury.turbocorp.com (8.12.8/8.12.8) with ESMTP id k51Hv7Ui001891; Thu, 1 Jun 2006 13:57:08 -0400 Message-ID: <447F2A73.3080104@turbocorp.com> Date: Thu, 01 Jun 2006 13:57:07 -0400 From: "John R. Allgood" User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060411) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Marlowe CC: pgsql-admin@postgresql.org Subject: Re: Postgres Backup Questions References: <447F049E.2000408@turbocorp.com> <1149179444.25526.139.camel@state.g2switchworks.com> In-Reply-To: <1149179444.25526.139.camel@state.g2switchworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/5 X-Sequence-Number: 21967 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 ...