-----Original Message-----
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Curtis Preston
Sent: Monday, January 21, 2008
8:30 PM
To: Dominik Pietrzykowski;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] FW: One
Client Per Policy
>Also,
have you haven't mentioned the issues with Nbpem when you have so many
policies. It takes ages to run through policies and start kicking off jobs ie
about 1hr for 500+ policies and 1500 clients. With 6000 policies I would >hate to see how long it
takes, do you ever bounce netbackup on that system ?
>>This is only an issue in pre-6.0, and I still found
it manageable with 2000 policies. (It took about 1.5 hours at the
beginning of the backup.)
> have seen this happen in a 6.0 environment
The, FWIW, I think something isn’t right.
Somebody replied to me that has almost 7000 policies with no ill effects.
>>Not if you use the “Summary of all
policies” view. It puts them all in the same window. Then you
can shift-select, change your window, and voila!
> can’t get this to work, it still brings up each
policy in a separate window !!!
Hard to help you with out seeing it. But it works for
me. I select ‘summary of all policies,” then schedules.
Then a listing of all of them is displayed in the right panel. I
can then do a shift-select selection of all of the schedules that I want to
change (with the limitation that they must be the same policy type (e.g.
Standard, Windows)), and then right click and select Change/Modify. I
then get a change schedule window like I normally do. If any of the items
that are schedule-specific, they are grayed out (e.g. Schedule type). (I
think if you select all full backups in one shift-select, you can change them
to be some other type, but if you select fulls and incrementals in the same
selection, the backup type is grayed out.) But then you can go to the
Windows tab, change what you want, and click OK and wait while it updates them
all.
>Swings and
roundabouts. I guess we’ll have to agree to disagree.
Right side of the road,
left side of the road. ;) It’s ok. Not everybody has to agree
with me. Only I have to agree with me. (Cause if I don’t,
then I’m crazy.) I just enjoy the discussion.
Cheers.
From: Curtis Preston [mailto:cpreston AT glasshouse DOT com]
Sent: Saturday, 19 January 2008
4:24 AM
To: Dominik Pietrzykowski; Randy
Samora
Subject: RE: [Veritas-bu] One
Client Per Policy
You didn’t send your reply to the list. You only sent
it to Randy & I, so I won’t copy the list on my reply to you.
>I use
multiplexing to stream as many clients to a drive that I can and so far it has
been streaming well. With single client policies you must be using some DSUs as
I'm not sure how you would do it with tape drives. They would be >tied up by single clients
wouldn't they ? I only have a few DSUs so I have to multiplex a lot of my stuff
to the tape drives.
NBU will mpx data from multiple policies together. This
is a non-issue.
>Also,
have you haven't mentioned the issues with Nbpem when you have so many
policies. It takes ages to run through policies and start kicking off jobs ie
about 1hr for 500+ policies and 1500 clients. With 6000 policies I would >hate to see how long it
takes, do you ever bounce netbackup on that system ?
This is only an issue in pre-6.0, and I still found it
manageable with 2000 policies. (It took about 1.5 hours at the beginning
of the backup.)
>>
If you're a GUI person, all you need to do is shift-select all the
>> policies you want to change in the GUI, make the
modification you want to > make, then save. NetBackup will update all
of the policies.
>Yes,
it brings up all the policies but in separate windows and you change them
individually. This takes ages but with a single policy it's easy.
Not if you use the “Summary of all policies”
view. It puts them all in the same window. Then you can
shift-select, change your window, and voila!
>I'd
rather add a client to a policy than add an extra policy ie stop issues like
the nbpem scheduler delay after start up.
I get this is easier, but I maintain that the other way is
easier in the long run. What _I_
do, BTW, is I copy an existing policy, then change it’s client. That’s
ALMOST as easy as just adding a client to an existing policy.
