Any considerations in having a large number of policys

[JayKoonz]

Right now, we're pushing 200 seperate policys, for a bunch of reasons. Mgmt wants a seperate policy for each client for tracking purposes. We have multiple policys for each oracle instance due to different retention cirteria that rman can't specify from that end. Seperate policys for the sql or exchange databases on some servers. Seperate policys for oracle logs. etc/etc/etc

Anyone know of any problems associated with having a large number of policys ? Or do some of you out there have alot more than we do ?

 

[Stumpr]

The extra files can be handled by NetBackup but it can cause a strain on the backup administrator. One thing to consider is the bpsched wakeup interval. You may want to increase the time between wakeups. Especially if you do any logging of bpsched

Bob Stump
Incorrigible punster -- Do not incorrige

 

[lenski]

Tell Mgmt that it's inificent to have one policy per client if there is no real need. You could have faster backups with use of multiplexing. If they want it for tracking purposes then they should buy you advance reporter. That said it is sometimes handy to have them seperate if you want to make changes to the images later, i.e. extend the expire date for one client. I'm also running about that number because Lotus Notes does not like to share.