I would also look at the save set status because by default, NW does not read a 
suspect save set. 

There is a known issue with NW cloning/staging a disk backup at least for NW 
7.6.1 & 7.6.2:
When encountering a write problem, NW will set all remaining save sets in his 
worklist to suspect.
You are right - as this is a write problem, it should not happen to the source 
(disk) media but in fact it does. Now, depending how you clone/stage, let's 
assume that this could only occur for a single save set. Before you start a 
retry, you must first clear the suspect flag. If not, it would be obvious for 
NW to use a save set from another media during a retry. And the only chance it 
has is a(n incomplete) tape instance.

I would at least look in this direction.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER