I am trying to understand your first question but more interested in you comment regarding the upgrade from 4.6.8 to 5.1.1. Here are some very specific questions that may take us closer to why your asking about the excessive time and events.
1. How big was your database before you attempted to upgrade?
2. Did your upgrade compatibility run successfully?
Let's start there.
- The database is 2.67 GB.
- Yes, i did upgrade compatibility run successful.
So far so good. Your database is tiny and the pre-check is aok. Moving forward;
1. The events you spoke of, did you detect the 10K events from the events folder?
2. Are the dates of those events current or older than a week?
3. How many clients you managing with ePO?
4. How much memory?
5. How many CPU's?
The content in KB article KB79561 should help answer your questions: McAfee KnowledgeBase - ePolicy Orchestrator 5.1 database size warning during upgrade
The reason you see this message is explained in the KB, but I will share it here — if upgrading to 5.1.1 from ePO 4.x version there is a check made against the DB tables listed below.
If any the tables listed will be modified by the ePO installer and have over one million rows, a warning message displays before the installation starts. The SQL server needs significant reserve disk space to apply the schema changes to these tables. These changes take significant time to complete, causing the ePO upgrade to potentially run for many hours.
This is the message that displays at the start of the upgrade:
You should purge those event tables listed above prior to upgrading to help decrease the time it takes for the upgrade to complete. You should be able to create Server Tasks that will do this for you. Here's a partial screen shot of the Server Task Builder actions list that includes several purge event selections. FYI, the table ePOProductEvents contains client events, the table EPOEvents contains Threat Events.
Hope this helps,
~ Patt ~
If you have unprocessed events accumulated into \DB\Events folders then before upgrade.
1. Please stop Event parser service.
2. Cut and paste \Events folder outside ePO directory.
3. Please start Event parse service and run installer.
thank you for the hint.
I will apply your suggestions and let you know about the effects of work.
where you can find the installation log file?