Doing automatic clones immediately after a backup finishes just isn't cool 
anymore - too much tape contention issues.

Before I launch my crafting of a script to do cloning after "backup prime 
time", I thought I would ask the folks here if they have any gotchas or good 
things learned from when you did the same thing.

I am running V7.5, which is what I've been waiting for since the nsrclone 
program is much improved; it has many of the selection features found in 
mminfo... much of the gathering SSID/CLONEID pairs to use for cloning will be 
eliminated with the new nsrclone functionality.

>From the V7.5 release notes about nsrclone improvements:

Script-less command line improvements for cloning

There were limitations with the nsrclone command that required complex 
mminfo/nsrclone wrapper scripts to extend certain features such as save set 
selection.

New in NetWorker 7.5

The need for mminfo / nsrclone scripting is now reduced or eliminated. The 
nsrclone command provides numerous selection criteria for save sets and cloning 
objects. You can also use the nsrclone command to change the browse time of a 
save set, if required.

For more information about using the new nsrclone command features, refer to 
the Cloning chapter in the NetWorker Administration Guide.

+----------------------------------------------------------------------
|This was sent by backupcentral AT easy48 DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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