I noticed a command line cloning (nsrclone -S) failure recently:

 % grep 'can not read record' daemon.log
 07/23/04 14:30:04 ansrd: ansrd_clone FAILED: errnum is -7 and errstr is can 
not read record 926 of file 2 on dlt tape nsr.103
 07/23/04 14:30:09 nsrd: media info: can not read record 926 of file 2 on dlt 
tape nsr.103

 % mminfo -v -q suspect nsr.103
  volume        client          date     time        size ssid      fl   lvl 
name
 nsr.103        thyme           07/03/04 12:57:17 3103 MB 3874720257 cb full 
/v/a/user.abc

 % mminfo -v -q 'name=/v/a/user.abc' nsrclone.019
  volume        client          date     time        size ssid      fl   lvl 
name
 nsrclone.019   thyme           07/03/04 12:57:17 3103 MB 3874720257 cb full 
/v/a/user.abc

This brings up some questions/issues:

 - How do I detect/report about cloning falures?  looks like grep'ing
   on something like "ansrd_clone FAILED" will do... but does anyone
   else have a better solution?

 - Can I detect when clone (destination) save sets are no good?
   (Yikes!  It's listed as complete and browseable!)  If not, perhaps
   I should write a script to mark bad clones as incomplete??

steve
- - -
systems & network guy
high energy physics
university of wisconsin

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