I need to get an estimate of how big my ePO database will be for approx. 4000 users/machines using ePO 5.3?
does anyone have any suggestions?
I currently have an ePO4.6 install and our database has increased to 35gb at the moment but don't think this is a realistic size!
It's depend which product are using? VSE/DLP/HIPS etc. each product can increase the database size.
Try first to reduce the size of the db.
I would suggest to run below SQL Query on ePO DB, to find out the top 10 events which are filling up you ePo DB
select top 10 E.ThreatEventid, EF.Description , Count(E.ThreatEventID) from epoevents E inner join EPOEventfilterDesc EF
ON E.ThreateventID = EF.EventID
Where EF.Language = '0409'
group by E.ThreatEventid, EF.Description
order by Count(e.ThreatEventID) Desc
This is will help you to understand, which product is generating high events. If you have expertise in SQL, You can further play around and find out the machine which is generating more events.
You future reference, review the below articles:
1. Recommended maintenance plan for ePO 4.x database using SQL Server Management Studio (KB67184)
Also recommend to the below URLs to keep the ePO and DB in good health
2. ePO Ecosystem Health
3. Database Maintenance: Part 1
4. Database Maintenance: Part 2
NOTE: ePO 4.6.x has reached EOL on 31st Dec 2015 and McAfee strongly recommends to upgrade ePO to Supported version ie; 5.1.x or later. version 5.3.1 is latest version.
Just wondering what you mean by realistic ? Your db is 35GB, so that is a fact as real as it can be.
Controlling DB size is two things: purge data using purge server tasks and product tuning where you reduce the events generate at the source (products)
my customers are using EPO Environments with a DB size more than 100GB. From my Point of view there are some cirsumstances which can affect your database size. YOu can use different Support documents for databse sizing. But at the end of the day it depends on your configuration.
- The managed products (VSE/HIPS/Application Control.....)
- The product Settings: One customer generated 4 Million Events per hour with one wrong Access protection rule.
- How log the Events should be stored.