• How frequently benchmark audits are performed.
• The number of systems audited.
• How long you want to retain audit results.
The tables used to calculate server and database requirements are based on tests
of the software in the following distributed environment:
• McAfee Policy Auditor server
• Four-processor, Intel Xenon 2.0GHz Core server
• 4 GB of RAM
• Windows 2003 Server 32-bit R2, Service Pack 2
• RAID array 5 hard drive for local storage
• Database server
• Four-processor, Intel Xenon 2.7GHz server with hyper threading
• 4 GB of RAM
• Windows 2003 Server 32-bit R2, Service Pack 2
• SQL Server 2005, Service Pack 2
• RAID array 5 hard drive for local storage
Effect of differential auditing results on database size
McAfee Policy Auditor increases database size an average of 760 KB of space per
new system audited. The differential audits feature causes the increase in database
size to decrease significantly after the first audit.
The Index Configuration server setting also affects the size of the database. If you
use the Minimal Indexing option, the database will be smaller than if you use one
of the other options.
The ultimate database size cannot be calculated accurately prior to deploying
McAfee Policy Auditor, but can be estimated approximately 3 months after beginning
a phased rollout. Use the database storage sizing estimates to determine the initial
database size for new systems and new audits.
Estimating database storage requirements
You can estimate the average amount of hard disk space needed to store new
McAfee audit results.
1 Determine the auditing requirements for your organization, including:
• The number of audits you will be performing.
• The frequency of each audit. For example, 20 audits once per quarter, 5
audits once per month, or one audit once per week.
• The number of systems covered by each audit.
2 Use the example and the table in Database sizing example and requirements
table to estimate the database space required for each audit.
3 Add the values for each audit. The sum is equal to the size of the database
required to store the audit results for one year.
4 Determine the length of time you want to store the audits and adjust the
database accordingly. For example, if you intend to store the audit results for
Pre-Installation Tasks
Database considerations and support
17McAfee Policy Auditor 6.2.0 Installation Guide
(20 paginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales