I ran the Problems report this morning to look through.  I'm finding
numerous entries like the following, usually clustered:

4/20/2007       9:36:39 AM      masterA         Error   0       General Bad
image header: Windows_Differential_Perimeter_1137677808_INCR, error: file
read failed (13)

We're running 6.0MP4, FYI.  I tried to use bpimagelist to find out more, but
I'm unsure how to do that.  I'm figuring that the entry just above the line
included is the culprit box.  But concatenating the '_1137677808' to the
server name with -backupid returns nothing.  Since the
'Windows_Differential_Perimeter' is a schedule name, I don't know what to do
with the info.  Are the images still floating around?  How can I locate
them, if so?

Thanks,
Jason

------------
Jason Brooks
Computer Systems Engineer
IITS - Longwood University
voice - (434) 395-2034
fax - (434) 395-2035
mailto:<brooksje at longwood.edu> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3332 bytes
Desc: not available
Url : 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070423/cfba68c3/smime.bin