Thanks for the list of possible san causes of backup aborts/corruptions.
How do you prevent these events from interfering with Networker?  Is there
a way to prevent them?

We have a very active network of machines which require work from time to
time.  We can't prevent that work from happening just because a backup is
running on another, separate machine.  Nor can we sacrifice a backup
because of unexpected, maintainence work somewhere else on the san.

Do you just look for the errors and re-run the backup or is there a fix
available which will trap for and/or block these events?

We've been chasing down these mysterious io, decode block errors for some
time and were quite surprised when we saw an mt status command appear
to cause an immediate abort on a backup.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=