I just tested and it looks like you need to just turn on the number of
copies to 1 to deactivate ITC (f the first pool is still good for the
single-copy)

To enable ITC again, set the copy count to 2 and you'll have to resend the
pools again.  This, of course, is if you use the bpplschedrep command at the
CLI.

If you used the command line to change the number of copies to 1, the
SCHEDPOOL settings stay the same.

Then you could change the count back to 2 when you're done, and supply the
SCHEDPOOL values back to the command with the "-schedpool <pool1>,<pool2>"
method.

A bit messy, though.

Easier might be to exclude, again via the CLI, the run date you don't want
from backup.  Then, again with the CLI, add new schedule with your one-off
parameters.  You could schedule the one-off with a specific include calendar
date or just run manually using bpsched.

Options - although kinda sucky ones.


-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Paul Keating
Sent: Monday, February 06, 2006 2:06 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] chaning ITC


I've got close to 100 policies, each with 2-3 schedules, and almost every
schedule has ITC enabled (2 copies of every backup.)

I want to disable ITC for a night to do some tests, but dang, it's a pain in
the butt to change them all.

I can't change the global value for max copies to less than 2......thinking
my best bet is to copy usr/eopnv/netbackup/db/class aside, turn off ITC in
every schedul, then restore the copy to reverse the changes.
annoying that you can't turn off "multiple copies" without losing all the
configuration (ie, when you turn multiple copies back on, you have to
reconfigure every stu/pool/ret.)

Any better ideas?

Paul