In article <45ccd559-d45a-4a9b-8b4b-5bfa078be4af@f3g2000hsg.googlegroups.com>,
mvsguy <kkinney@fuse.net> wrote:

[second followup - wjv]

>> Whats your time worth?
>D
>My time? I have to show up at least 8 hours each day. I might as
>well do some work...

>I've cleverly disguised my handle to cover the fact that I'm an MVS
>guy. Mainframes. I know how important DR is.
>I've had a full on disaster caused by IBM applied hardware
>maintenance. We only lost 18 hours of data. Later that month, we did
>our first DR test. We did amazingly well.

>Thank you both for trying, but buying software is simply not in the
>cards.

IMO - as I mentioned in a prevous post - VERIFYING that the data
on the tape matches exactly is quite important. And actually
when you perform a restore, run the verify software to make
sure the data on the HD now matches the tape.

Years ago - one my Esix 5.3 [system] [I got tired of waiting for
the SCO 5.3] I ran a program call cktar - which acted remarkable
like the bit level verify on a program called C-tar that came out
a bit later.

If you want to put in a bit of effort search for the alt.sources
hierarchy [probably stored somewher] and look for cktar by
Wareen Tucker. It will be in the fall of 1990 archives, and
it will be about a 14K .c file tucked inside a shar archive.

I used to use it all the time when I was backing up to floppies,
as it would find an error every few disks.

Bill
--
Bill Vermillion - bv @ wjv . com