>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.)

I have seen this happen in a 6.0 environment

>> 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 can’t get this to work, it still brings up each policy in a separate window !!!

>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.

 

Swings and roundabouts. I guess we’ll have to agree to disagree.

 

 

 

 

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.