Content indexing - high CPU utilization

Hi ​@Nikos.Kyrm,

I would like to share the below document first to validate the configuration,

https://documentation.commvault.com/2024e/essential/guidelines_for_exchange_online_access_nodes.html

Guidelines for Exchange Online Access Nodes

With Content Indexing
If you use content indexing, use the following guidelines.

Assumptions

The guidelines are based on the following assumptions:

• The average mailbox size is 5 GB.

• The average number of messages in each mailbox is 50,000.

• The average message size is 100 KB.

Ensure that the Exchange server is running with the supported OS version.

https://documentation.commvault.com/2024e/essential/system_requirements_for_exchange_online.html

Ensure to exclude all the CV folders from the AV scanning,

https://documentation.commvault.com/v11/essential/antivirus_exclusions_for_windows.html

Regards,

Wasim

Hello ​@Wasim and thanks for your reply!

We are in “Large” environment with around 10,000 mailboxes.

Because in this case is also enabled Content Indexing, in the first “initial” backup jobs I noticed high CPU utilization in Content Index jobs (after backup jobs)!

So, Im looking a way to split this CPU high utilization to another MediaAgent.
To achieve that, must configured new MediaAgent also as Access Node of Exchange online? Because already tried to add a secondary node to associated o365 INDEX, but still, high CPU utilization is only to 1st MediaAgent.
 

Merry Christmas & Happy New Year 🎉🎉🎉

​@Nikos.Kyrm FWIW when I was having this problem, I found that AV was scanning each file. Once the exclusions were reapplied, the CPU utilization went to normal and content indexing is much faster.