Automatic cloning is based on a savegroup and is a single-threaded process.
For a given group, the NetWorker software runs only one clone at a time, regardless of
the parallelism setting.
Other groups that have auto-clone configured are able to run in parallel. However,
they will also run only one clone at a time, assuming that there is no contention for
volumes or devices.
Using scheduled clone job you can manage 30 parallel cloning sessions (edit /nsr/debug/nsrcloneconfig).
However , in my opinion, if you have a small environment and few savesets for each client you can use automatic cloning (also for "save set completion") . Instead if you need regular/daily replication of a lot of client and savesets I suggest you to use scheduled cloning job .
ZennaroNicola
1 Rookie
•
88 Posts
666
0
Posted January 28th, 2016 01:00
Hi ,
Consider the following:
the parallelism setting.
they will also run only one clone at a time, assuming that there is no contention for
volumes or devices.
Using scheduled clone job you can manage 30 parallel cloning sessions (edit /nsr/debug/nsrcloneconfig).
However , in my opinion, if you have a small environment and few savesets for each client you can use automatic cloning (also for "save set completion") . Instead if you need regular/daily replication of a lot of client and savesets I suggest you to use scheduled cloning job .
-Nicola