We have a group that runs on the weekend, set to automatically clone. One 
client is still trying to clone, as evidenced by a saveset query in NMC. 
It shows one SSID that's "browseable has clones" and "browseable cloned on 
07/25/10", which refers to the backup and its clone, respectively, both 
successful.

However, there was apparently an earlier failed attempt to back up that 
same saveset, as reported here by mminfo (different SSID):

# mminfo -ar 'volume,pool,ssid,client,name,ssflags,clflags,sumflags' -q 
'ssid=3746180500'
volume  pool         ssid       client   name    ssflags clflg  fl
001041  backup_pool  3746180500 client1  saveset1  vrEi   Es   tE
001059  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001286  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001289  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001305  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001358  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001790  backup_pool  3746180500 client1  saveset1  vrEi   Es   mE
001792  backup_pool  3746180500 client1  saveset1  vrEi   Es   hE


Yet, NMC reports a clone status of "in-progress suspect" for this SSID...

Two days ago, I had to kill this group due to a (different) hung client, 
during backups before cloning even started. I manually assembled a list of 
SSIDs and ran nsrclone against that list, which did NOT include this SSID.

Any idea why Networker would be trying to cloned a failed saveset from an 
aborted group?

Thanks.

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