since these are the client's server hosted with us we backup specific 
data/directories and the policies are based on files we backup. Schedule and 
mpx values  doesn't matter. They all have same retention (except for few 
sun/oracle boxes).

Thanks

-----Original Message-----
From: Vapiwala, Kevin V [IT] [mailto:kevin.v.vapiwala AT citigroup DOT com]
Sent: Monday, November 17, 2003 11:47 AM
To: Ajay Sharma; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Number of policies/ Performance Hit


how do you break up the policies? In the past we use to break them up by 
Network segments and restrict jobs per policy to alleviate network constraints 
from a particular network segment.



-----Original Message-----
From: Ajay Sharma [mailto:Ajay.Sharma AT hostcentric DOT com]
Sent: Monday, November 17, 2003 1:58 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Number of policies/ Performance Hit


We are currently running netbackup 4.5 Data center. We currently have over 200 
clients server within 73 different policies. I  dont see any performance issues 
for now as far as data transfer rate is concerned. Most of the schedules are 
configured as similar. I was just wondering how the multiplex and no. of 
concurrent jobs will be managed. Currently the clients are not able to finish 
the jobs withing the specified period of time.

Any guidelines/suggestions on the policy/schedule attributes and how to manage 
them?

Thanks
Ajay.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu