We are about to deploy 5.1 to our user community. We have about 1500 Person accounts (staff who can create service calls using the web interface) and about 100 Specialists in about 25 Workgroups who will be assigned work orders based on the incoming service calls (estimated at about 200 service calls a day and about 50 new work orders a day). We are wondering how much space to allocate to the various log files, cache files, etc. to insure about one week of logging.
The HP Service Desk Administrator's Guide (Chapter 12) has the following documentation:
BinSizeLimit=n Sets the maximum size of binary log files to n bytes before it rolls to the next file. Default is 10000.
BinFileLimit=n Sets the maximum number of binary log files to generate before throwing away log entries. Default is 10.
TextSizeLimit=n Sets the maximum size of text log files to n bytes before it rolls to the next file. Default is 10000.
TextFileLimit=n Sets the maximum number of text log files to generate before throwing away log entries. Default is 10.
Does anyone have some real world experience or suggestions regarding log file size? If our number of Persons doubles, does that mean our log file sizes should double? Any info will be appreciated.
Not to sound like a party-pooper, but with OVSD 5.1, log file sizes are going to be the very least of your worries. We've done all sorts of different stuff with our log files but with support it always comes back to "anything but default can cause a performance issue" (which you should have more than enough of in this version).
To give you a sense of scope, we have about 10 times your amount of customers, 4 times the number of specialists, and depending on the day 2 - 4 times your call volume. To my knowledge we haven't dedicated any thought to the size of our log files, and for a couple months we even had increased verbosity running.