Hi Mike,
hunch, and prove (sort of)
Event Category: Storage File Watch
What happens is the following
backupprogram runs cmd file that places EV-index+store in backupmode.
backup
backupprogram runs cmdfile to first set triggerfile in partitions, then takes ev out of backupmode. (check to see if backup succesfull or not before placing triggerfile)
When EV comes out of backupmode, collect/migrate starts, as does some other stuff. What happens on this 1 server (the other 14 run fine) is that storagefilwatch.exe starts fine. It rattles away, doing it's job (I see the number of items awaiting backup going down from 1.947.333 to 1.932.250 in an hour)
Then, it starts logging the 7109 errors. (many really quick)
After about 10 minutes, I see StorageFileWatch.exe running at up to a max of 96%cpu time, consuming more and more memory.
Additionally, there is an event logged (not at hand sorry), which indicates a virtual memory error (something with unable to proces request due to vm being low)
Restarting storageservice helps for a shortwhile. I need the SFW.exe to finish. My other 14 servers have less than 25.000 items awaiting backup (normal average operation between backup and archiving window). This one server sits on over 1.9 million.
I do not know what happened, but suspect an issue with backup somewhere. Due to the amount of events, I cannot go back in the eventlog anymore. I do have a case (also, number not at hand)
I now have added 2GB more to the server (running now at 4GB RAM). Hopefully it cleans out tonight. Backup has been disabled, tasks are in report mode. I fear I need to run EVSVR, but the manual is not too clear.
More tomorrow.
Thanks.
Regards. Gertjan