I have a client definition that enumerates folder names explicitly (i.e.,
in the saveset definition, I list 10 folder names; I don't use ALL). We do
this for speed reasons - this way, I get more folders being backed up
simultaneously than if I just said ALL. This works well.
Now, here's a question - if I changed this set up so that I had 2 client
definitions for the same client - one entry with 9 of those folders, and
the other entry has the other folder. And now my group, instead of having
only 1 client (with 10 folders enumerated), now has 2 clients entries
(for the same client, mind you), one with 9 folders, and one with one
folder ... will it still execute all 10 folders in parallel? Or: will it
execute the client definition with the 9 folders in parallel *first*, and
the other client definition will sit and wait until the job with the 9
folders finishes first?
(this goes to a related question I will be sending later, on using 2 FTD
devices (or AFTD devices) with the same client, and how to choose which
job writes to which device)
So: will a group with 2 client definitions like I described above backup
all 10 folders in parallel (based on parallelization settings, of course),
or will it do 9 in parallel, and the remaining folder sequentially?
If it is 9 then 1, what about if I use a second group for that client
definition with 1 folder? Will using 2 groups allow me to have all folders
being backed up in parallel?
Thanks
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
|