My experience with cloning is that it's best to generate list of saveset, 
excluding the suspect, in progress, aborted etc and then clone them via 
nsrclone in an separate process.
With careful planing of groups, pools and retention policies this would 
work the best, the list users can provide you the script needed to to 
check for failed clones, doublecheck the cloning and any other relevant 
methods to ensure successful cloning, automatic group cloning is somewhat 
buggy and will require monitoring, however,its easiest to setup and use.
If you use external scheduler that would work the best.
There are many ways to generate saveset list and execute nsrclone, list 
users can provide you the examples.
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