How to monitor the Disk Space for Caching Requirement This section contains the following subsections: • Distributed Deployment • General Tuning • General Tuning • Offloading units to other agents NOTE: If you are generating weekly and monthly reports, and this process is taking upwards of an hour or so to generate each scheduled report, you need to setup your GMS for nightly optimization. Contact SonicWALL Support for step-by-step procedures. Working space is required to run reporting queries and to perform nightly optimization (if enabled). The nightly optimization is executed on a day’s worth of syslogs at a time that are stored in the reporting database, so knowing the average number of syslogs per day uploaded to the database is the first step. You can determine this number by accessing the TSR from the “/appliance” interface of the GMS server you are interested in. The following TSR example shows the calculation for estimated work space required, using the March 2012 entry (raw_201203): First Calculation (average syslogs per day) Formula: (number of syslogs / number of days = syslogs per day) Number of syslogs: 40,824,667 Number of Days: 15 Calculation: 40,824,667 / 15 = 2,721,644 (2.7 million syslogs) So the average syslogs collected per day in March is 2.7 million syslogs. The previous TSR approach is a workaround to determine how many syslogs your system is getting per day. Second Calculation (working space required for optimization) Formula: (Number of millions syslogs per day x 2GB = x GB) if this equates to less than 20GB, use 20GB. Number of syslogs per day (use number from first calculation): 2.7 million Calculation: 2.7 x 2GB = 5.4GB Because 5.4GB is less than 20GB, use 20GB. Make sure that in the previous example you maintain at least 20GB of free disk space.
