Shutdown and startup order of Enterprise Vault services

Task Controller i would restart every day, there are numerous MAPI leaks way outside of Enterprise Vaults control that just occur over long periods of time.
Even with the internal recyle of mapi tasks that EV does itself internally after so many operations, there still seems to be a lot of handles that reside until the task controller restarts them all.

As for storage, i know that you're not meant to have to restart it, however there are also some memory leaks with in things like StorageOnlineOpns, and if you are heavy on the export side through Discovery Accelerator or Move Archive, then yu could find that keeping the storage service permanantly running will also cause memory and performance issues.

For instance we had an issue where we were actually doing DA Exports, PST Exports via the API and Move Archive and it would cause some machines to become unresponsive to the point where they needed to be rebooted.

After getting the Storage Service to restart every night, this has no longer been an option.

But for 4000 users though?
What i would suggest really is restart of Task Controller every night and restart of all the services once a week, maybe on a sunday or some such?