cancel
Showing results for 
Search instead for 
Did you mean: 

Storage Crawler consuming high CPU

I have a customer who has EV 10.0.2 & he faced issue with storage as disk was full few weeks back so he stopped indexing, arranged for a new disk and when he tried to start the service again, he got error "Service cannot be started", now we've got the issue resolved after reinstalling indexing modules however the new disk is getting full very soon. He enlarged the drive of the temp folder but it is eating up a lot of space. He has now enlarged it to 200 Gb which is now almost full with temp files within 2 days.

The storage crawler meanwhile is taking up 53 % of total CPU time.
And it is generating error messages in the event log:
StorageCrawler FetchAheadThread thread [ThreadId: 8576] have been forcefully terminated.

For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=10.0.2.0&build=10.0.2.1112&error...

Customer is manually cleaning up the temp files time to time, but he says he shouldn't be having to do this on a daily basis.

He wants to know why it is generating so many temp files.
He would also like to determine why there are errors on the storage crawler and why it is taking 53% of CPU time.

 

Please help !!

 

1 Solution

Accepted Solutions
Accepted Solution!

This is already resolved by

This is already resolved by implementing DelOldFiles for admin registry key. Thanks anyway.

View solution in original post

5 Replies

What about a dtrace? Are

What about a dtrace? Are AntiVirus exclusions correct?

Regards. Gertjan

Yes, would need to see if the

Yes, would need to see if the StorageCrawler process is cycling on a certain item for some reason.  Could be a large item that is causing larger temp files to be created. 

Accepted Solution!

This is already resolved by

This is already resolved by implementing DelOldFiles for admin registry key. Thanks anyway.

View solution in original post

Re: This is already resolved by

I know this is an old thread, but I am unable to find anything showing the steps for the DelOldFiles registry key.

We're currently having issues with the EBV storage crawler continuously spiking the CPU and hanging there, even after restarting all EV services.

Re: This is already resolved by

maybe she was talking about this: https://www.veritas.com/content/support/en_US/doc/115749471-137825802-0/v9026420-137825802

DelFilesOlderThanHours

Location

HKEY_LOCAL_MACHINE
 \Software
  \Wow6432Node
   \KVS
    \Enterprise Vault
     \AdminService

Content

DWORD

Description

Specifies the number of hours since a temporary file was last accessed before it becomes eligible for deletion. The default is 1.

Additionally, you can set DelFilesOlderThanHours to 0 to force immediate deletion of all files matching DelFileTypes except for folders, read-only files, and files that are currently in use.

If you modify DelFilesOlderThanHours, the change is picked up automatically at the end of the existing period. So, for example, if the current period is 1 and you change it to 24, the change takes effect at the end of the 1 hour period. However, the change will be picked up immediately if you restart the Admin Service.