Sometimes, guest file indexing takes a long time

[stephanreipoeler]

Hello,

We back up a file server with an extremely large number of files and perform guestfile indexing on the drive where the work files are stored. Mostly the indexing takes about 1 hour and 45 minutes, but sometimes it takes up to 18 hours. Does anyone have an idea why this may be? At first I thought, someone has stored a large number of files on the server. But that can not always be the case.

[PTide]

Hi,

Please contact our support team directly so they can investigate and post your case ID.

Thanks!

[csydas]

Hiya Stephan,

We had a similar issue in our shop, and it was just a resources problem. Try bumping RAM+CPU on the VM at first just to see if it makes a difference.

[foggy]

Indexing performance does indeed depend on the number of files in the guest system. But in your case the difference is too big, so please investigate with the help of support.

[fja]

for your information: experience issue on new Windows2019 VM. Indexing running for 10-14 hours, as apposed to 2-5 min on other similar machines.

Investigating situation right now, I found 'Update Orchestrator Service' consuming 35% CPU on the VM. Ending task made veeam indexing finish in 2 minutes…. So: a clue at least….

Had this occur on a few new Win2K19 servers - so far never on W2K16 or older

[wishr]

Hi Fja,

This is indeed very interesting.

Update Orchestrator Service is responsible for handling windows updates which in some situations may cause unusual resource consumption. There is a variety of topics on the internet about the same issue or very similar which suggest performing CHKDSK, removing AV software, cleaning windows update history and restarting the related windows update services.

Thanks