<font size=2 face="sans-serif">OOPS... mmbackup uses mmapplypolicy.</font><br><br><font size=2 face="sans-serif">Unfortunately the script "mmapplypolicy"
is a little "too smart". When you use the "-N mynode"
parameter it sees that you are referring to just the node upon which</font><br><font size=2 face="sans-serif">you are executing and does not pass
the -N argument to the underlying tsapolicy command. (Not my idea,
just telling you what's there.)</font><br><br><font size=2 face="sans-serif">So right now, to force the parallelized
inode scan on a single node, please just use the tsapolicy command with
-N and -g. tsapolicy doesn't do such smart argument checking,</font><br><font size=2 face="sans-serif">it is also missing the nodefile, nodeclass,
defaultHelperNodes stuff ... those are some of the "value add"
of the mmapplypolicy script.</font><br><br><font size=2 face="sans-serif">If you're running the parallel version
and with message level -L 1 you will see this message:</font><br><br><font size=2 face="sans-serif">[I] 2015-11-10@15:57:47.871 </font><font size=3 face="sans-serif"><b>Parallel</b></font><font size=2 face="sans-serif"><b>-piped
sort and policy evaluation</b>. 5 files scanned.</font><br><br><font size=2 face="sans-serif">Otherwise you will see this message:</font><br><br><font size=2 face="sans-serif"><b>[I] 2015-11-10@15:49:44.816 Policy
evaluation. 5 files scanned.</b></font><br><br><br><font size=2 face="sans-serif">But ... if you're running mmapplypolicy
under mmbackup... a little more hacking is required.</font><br><BR>