
two years, double the database size obtained in step 3. If you intend to store
the audit results for six months, divide the database size by two.
Database storage example and requirements table
The requirements table for database sizing can help you calculate the the
approximate disk space needed for your McAfee Policy Auditor database.
Requirements table for database sizing
Use this table to estimate the required size of your database. These estimates are
based upon the average size of benchmark audit results. Your needs may vary.
50,000
systems
20,000
systems
10,000
systems
5,000
systems
2,000
systems
1,000
systems
Per system per year
Database size (GB)
Total
audits
Frequency
68271473111 yearly
1275527145322 yearly
342137683414755 yearly
6842371376827141010 yearly
1,36754727313755272020 yearly
273109552711541 quarterly
54721910955221182 quarterly
1,3675472731375527205 quarterly
2,1881,094547273109554010 quarterly
5,4692,1881,0945472191098020 quarterly
820328164823316121 monthly
1,6416563281646633242 monthly
4,1021,64182041016482605 monthly
8,2033,2811,64182032816412010 monthly
16,0466,5633,2811,64165632824020 monthly
3,5551,42271135514271521 weekly
7,1092,8441,4227112841421042 weekly
17,7737,1093,5551,7777113552605 weekly
35,54714,2197,1093,5551,42271152010 weekly
71,09428,43814,2197,1092,8441,422104020 weekly
24,9519,9804,9902,4959984993651 daily
49,90219,9619,9804,9901,9969987302 daily
Calculating database storage requirements
A corporation follows this policy for running audits:
• The company retains audit results for one year.
• One audit runs every three days on 2,000 systems. The table does not include
this value, so we approximate this to two audits per week running on 2,000
systems.
• Five monthly audits run on 5,000 systems.
Pre-Installation Tasks
Database considerations and support
McAfee Policy Auditor 6.2.0 Installation Guide18
Comentarios a estos manuales