v11.1 and omscan.server process

[mnauta]

I just installed V11.1 to solve the MANY server freeze up and tomcat problems. I noticed that omscan.server is running, that is to index the messages correct? This will take over 24 hours if I recall correct from my V10 upgrade.

Should I stop my nightly backup cron job which stops scalix and tomact, will that messup the omscan.server indexing?

Thanks
manuel

[mnauta]

never mind, the process stopped.

[KevinAnderson]

Omscan is a 2 part process.

1 part will run continually in the background, but won't take much in terms of CPU.

A second part would run much more processor intensively, and check the mail store for consistency. You can (and should) run it manually, I generally run it on Sat evenings. "omscan -Aavfx". Don't be too concerned about a few orphans and stuff, that's normal. You may need to run it three or four times before everything is 100% again...

The process that indexed the mail in the message store, is indexer, and it will aos be running still, but since the message have been indexed already, it will only run as new mail arrives, and therefore won't beat the machine for long periods of time like the initial upgrade to 11 did.

You may also have ran omtidyallu -M. Again, this would beat the machine, but it isn't necessary to run it again.

Kev.