Use 64-bit CPU hardware with the supporting operating systems. Reporter can run on both Red hat enterprise Linux version 5, or Microsoft Windows 2003 and 2008 servers. See the Blue Coat Reporter version 9.1.x readme file for the exact specifications.

Do not run Reporter on a Windows Primary Domain controller. Some large database queries can consume so much CPU time that authentication requests start to slow down or even stall.

Disk space and placement of access logs:

Upload your access logs to a separate server, and pull them down via the FTP protocol to be processed into the databases. If you can't upload them to a seperate server, have them uploaded to a seperate mount point, or Drive on the server you run Reporter on.

Only upload them every hour to ensure you don't overload your servers file system. To minimize load, Blue Coat recommends that you only process access logs once a day. By Default, Reporter is configured to check, and process, acess logs every ten minutes.

Create you database(s) on local mount points, or disk drives, on your server. If you create a database on a Disk drive, or Mount point (LINUX) other than the one the Reporter service runs on, it will not monitor it and alert you when you run low on space.

Ensure you always test how long a Report takes to run before you schedule it. This ensures that you allow appropriate time between scheduling each report.

Do not store more than 50,000 access logs in one folder. Reporter has trouble with more than this amount, when it comes to having to re-process them all at once.

Schedule Reporter to process it's access logs at 2 AM every day to avoid running reports, and processing access logs at the same time.

Do not upload more than a year worth of access logs to the same folder. By default, the ProxySG does not write the year into the name of access log, so after a year, Reporter sees the same name log file in the folder. The rename occurs as Reporter moves or rename the access logs once it has finished processing them . The file names will look like the following:

Origonal file name from the year before:SG_main__2100316010000.log.gzAfter an attempt to rename/move the access log file, it will name this file to: dup0001_SG_main__2100316010000.log.gz