Has anyone tried adjusting the Sybase ASA cache sizes for either NBU or 
NOM?

The 6.5.2 document updates introduces the dbadm tool, which amongst other 
things allows you to change the cache settings in the 
/usr/openv/var/global/server.conf file for NBU.

NOM has a similar file, documented in the Veritas NetBackup? Backup 
Planning and Performance Tuning Guide UNIX, Windows, and Linux Release 6.5 
dated October 1, 2008 (page 147) /opt/VRTSnom/var/global/nomserver.conf.

For NOM it also suggests rather than setting the Initial, Low and High 
cache values (-c, -cl, -ch) to just set the cache and lock it (-c and 
-cs).  The dbadm tool doesn't really like that - it doesn't break but if 
you use it to set the cache it just sets the -c value and leaves the 
-cs...which locks your cache at the initial size, which is sure to be a 
really bad idea.

I was wondering who had changed from the defaults, whether it helped, what 
it helped, and what really is 'small', 'medium' and 'large' - lots of 
clients, lots of images retained, lots of policies all starting at once?

William D L Brown


-----------------------------------------------------------
This e-mail was sent by GlaxoSmithKline Services Unlimited 
(registered in England and Wales No. 1047315), which is a 
member of the GlaxoSmithKline group of companies. The 
registered address of GlaxoSmithKline Services Unlimited 
is 980 Great West Road, Brentford, Middlesex TW8 9GS.
-----------------------------------------------------------

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