Just a minor correction, the number of copies is updated whan a saveset is 
starting to clone, which is why we run a script to find savesets that have 
2 copies and either an aborted or interupted clone saveset and reset the 
copies to 1  so that a clone script will later see it as valid for cloning 
again.

On Thu, 4 Jun 2009 13:20:18 -0500, Len Philpot <Len.Philpot AT CLECO DOT COM> 
wrote:

>> Mark Davis
>>
>> When running nsrclone on a list of savesets, and viewing the
>> Monitoring/Sessions tab, and with "Show: Clone Sessions", there is no
>> dynamic update showing the progress of the job. It simply shows the
<SNIP>
>> Has anyone else noticed this? Is there a workaround?
>
>If you can generate (or already know) a list of the ssids that are being
>cloned, you can run mminfo against that list and watch the "copies" field.
>Those with only one copy are not yet cloned. The totalsize (or sumsize)
>field will also give you a rough idea of the relative time to clone them
>based on their size.
>
>I realize that's not a whole lot, but it's more than nwadmin/nsrwatch will
>tell you.  :-)
>
>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
>=========================================================================

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