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 0C26F9FA040 for ; Thu, 1 Jun 2006 15:30:04 -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 50765-01 for ; Thu, 1 Jun 2006 15:29:58 -0300 (ADT) X-Greylist: delayed 00:28:39.746963 by SQLgrey- Received: from is.rice.edu (is.rice.edu [128.42.42.24]) by postgresql.org (Postfix) with ESMTP id 6877B9FA5D2 for ; Thu, 1 Jun 2006 15:29:58 -0300 (ADT) Received: from scan2.mail.rice.edu (scan2.mail.rice.edu [128.42.59.161]) by is.rice.edu (Postfix) with ESMTP id DFC21418D3; Thu, 1 Jun 2006 13:01:16 -0500 (CDT) Received: from is.rice.edu ([128.42.42.24]) by scan2.mail.rice.edu (scan2.mail.rice.edu [128.42.59.161]) (amavisd-new, port 10024) with ESMTP id 16944-09; Thu, 1 Jun 2006 13:01:16 -0500 (CDT) Received: by is.rice.edu (Postfix, from userid 18612) id 28887418D2; Thu, 1 Jun 2006 13:01:16 -0500 (CDT) Date: Thu, 1 Jun 2006 13:01:15 -0500 From: Kenneth Marshall To: "John R. Allgood" Cc: Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: Postgres Backup Questions Message-ID: <20060601180115.GH15172@it.is.rice.edu> References: <447F049E.2000408@turbocorp.com> <1149179444.25526.139.camel@state.g2switchworks.com> <447F2A73.3080104@turbocorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447F2A73.3080104@turbocorp.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: by amavis-2.2.1 at scan2.mail.rice.edu X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/12 X-Sequence-Number: 21974 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 >