Enterprise Vault scheduled services restart best practice

[goatboy]

Hi  

Running EV 9.0.2 and SQL 2008.

Looking to introduce a scheduled restart of EV services. Not sure if I've seen this requirement in the official Best Practises doco, but we've done it in EV8 and are looking for the same thing in EV9, to flush MAPI connections, etc.

However, given we have scheduled searches running in CA and DA, I don't want to interrupt them. Ideally I don't want to interrupt exports from CA and DA, but can live with that.

Proposed plan:

Restart the following EV services at 6AM nightly:

"Enterprise Vault Task Controller Service"
"Enterprise Vault Storage Service"
"Enterprise Vault Shopping Service"

Don't touch Indexing, Directory or Admin.

Will the above mean that scheduled searches in CA and DA continue running without interruption?

I asked Symantec about not affecting CA/DA exports, and they came back with:

"You would need to stop first the Accelerator Service on your CA/DA Server, recycle EV services, and then start again the Accelerator Service. This will pick off from where it stopped for both searches and PST exports" - that's a bit of a hassle to schedule, so I will live with interrupting CA/DA exports.

Any other ideas/comments/criticisms around regular EV services restarts?

Thanks!
 

[TonySterling]

If mapi is your concern just restart the Task Controller service and leave the others alone.

As long as Indexing is available the accelerator searches will be ok.

[Ameen]

What we are doing is we are restarting EV Task controller service everyday and it looks helping.

[goatboy]

we find restarting Storage service helps to bump journaling along, but the infrastructure is ancient, so this may not be required once we get new servers.

[Chris_Warren · Accepted solution]

Here is another option if your concerned with the stability of the MAPI connection:

http://www.symantec.com/docs/TECH68433
How to restart Enterprise Vault MAPI Tasks automatically.

Value Name: RestartAllMAPITaskIntervalMins 
Data Type: DWORD
Specify the number of minutes (decimal) to wait before restarting the MAPI tasks.Value

Name: RestartOnMAPIMutexError
Data Type: DWORD
0 = (Default) Do not restart MAPI Tasks when a MAPI Mutex error is reported.
1 = Restart MAPI Tasks when MAPI Mutex error is reported.

Hope this helps.