Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version Tektronix Network News Daemon (B 2.10.2 based); site lumiere.UUCP
Path: utzoo!linus!decvax!tektronix!lumiere!richl
From: richl@lumiere.UUCP (Rick Lindsley)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: dump(8) verification ?
Message-ID: <1206@lumiere.UUCP>
Date: Mon, 7-Oct-85 02:06:53 EDT
Article-I.D.: lumiere.1206
Posted: Mon Oct  7 02:06:53 1985
Date-Received: Wed, 9-Oct-85 03:50:44 EDT
References: <631@dicomed.UUCP> <129@amc.UUCP>
Reply-To: richl@lumiere.UUCP (Rick Lindsley)
Organization: Tektronix, Beaverton OR
Lines: 16
Xref: linus net.unix:5237 net.unix-wizards:12288
Summary: 

A relatively reliable way to check even a multi-volume tape is to do a
dumpdir (or restore -t, depending on your flavor) and, using awk or
sort or something, obtain the highest number inode that was dumped.
Then restore that file, doing it the *dumb* way (starting with tape 1,
through tape n). This will force restore to read each and every tape
and finally restore the last file on the last tape. This doesn't verify
the data on every file, but it does verify that all the tapes are
readable, that the labels you put on the tapes are correct, and that
the data on the tape is in a recognizable format. This was the test we
used to use at a leading university (Hi guys) before we packed away the
last full backups of a semester for three years.

If all you are interested in is tape errors, however, then as someone
else mentioned, dd is a very fast way of doing that.

Rick Lindsley