Re: anybody using Archecker with Onbar ?

Thanks John. Do you verify each and every onbar backup you make or just spot check them ? Our big instance takes about 4.5 hours to backup, so I am guessing it will take an equal amount of time to verify it. ======================== -<<Floyd Wellershaus>>- Database Administrator Unix Administrator email: fwellers@yahoo.com Home: 703-430-0805 Cell: 703-477-6045 ======================== http://www.one.org/ ----- Original Message ---- From: "Kennedy, John" <john.kennedy@logicacmg.com> To: Floyd Wellershaus <fwellers@yahoo.com>; informix-list@iiug.org Sent: Thursday, April 27, 2006 8:01:33 AM Subject: RE: anybody using Archecker with Onbar ? Hello Floyd, we here use onbar -v to verify our backups, I believe this just calls the archecker utility to verify the backups. There is an outstanding issue regarding Archecker failing when the backup is actually successful, this was noted when we ran it on an ontape backup however I am not sure if this same case for the verifications using onbar -v. I am investigating at the moment and will feedback to you with my findings. Cheers John From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Floyd Wellershaus Sent: 27 April 2006 11:59 To: informix-list@iiug.org Subject: anybody using Archecker with Onbar ? I am wondering if it is considered best practice by many to use Archecker to verify Onbar backups. I've never used it before. Is it worth the resources it uses on the system ( ie, a tape drive, database and system resources) ? Also, I notice that it does the equivelent of oncheck -cd, ce and cr on the backup tape. That seems to be a quick/alternate way to verify the data on our database. Any thoughts about that ? Thanks for any advice. ======================== -<<Floyd Wellershaus>>- Database Administrator Unix Administrator email: fwellers@yahoo.com Home: 703-430-0805 Cell: 703-477-6045 ======================== http://www.one.org/ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.