Video Screencast Help

Implications of restarting EV services and DA Accelerator services

Created: 14 Oct 2013 • Updated: 17 Oct 2013 | 8 comments
This issue has been solved. See solution.

Hi

Environment is EV 9.0.2

We currently restart the following EV services nightly:

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

We do this for historical reasons as we did it in our older EV8 environment, I believe it was to clear up MAPI sessions andkeep the system running more smoothly. Is this still necessary?

Does restart these EV services impact DA searches and exports? What's the impact?

Does restarting the DA Accelerator service impact DA searches and exports? What's the impact?

thanks

Operating Systems:

Comments 8 CommentsJump to latest comment

Kenneth Adams's picture

Hello, goatboy;

You should not need to restart those services every night, but those restarts should pose minimal impact on DA searches and exports.  Restarting those services has the following impacts:

- Enterprise Vault Task Controller Service controls all archiving operations, including adding items to archives and also restoring items to archives.  While this service is stopped, no mailbox, journal, file system, SharePoint, etc, archiving can be performed.  This does not affect DA searches, reviews or exports.

- Enterprise Vault Storage Service controls all operations involved with adding, removing, or exporting items from the archives.  With this service stopped, items cannot be added to or removed from archives.  Also, unless EV is installed on Windows Server 2008 R2, Legal Holds from DA cannot be added or removed.  If EV is installed on Windows Server 2008 R2, DA Legal Hold processing can continue as DA can cause the StorageOnlineOpns process to pick up and run.  Running DA searches is not affected with this service stopped, but accepting searches can be affected if Legal Holds are to be placed on the items being accepted.

- Enterprise Vault Shopping Service controls user restores through their mailbox client, Archive Explorer or the web browser.  With this service stopped, users cannot restore items.

Restarting the DA service (the Enterprise Vault Accelerator Manager Service - a.k.a., EVAMS) causes all running searches and exports to stop until the service is running again.  Those running searches and exports should pick up where they left off and continue until completion. While the service is stopped, no searches can run, no exports can process, and no reviewing of items is possible as the DA Clients will not be able to access the DA Customer database that contains the data needed to process the search, export and review requests.

I hope this information has provided the information you need.  If you need anything more, or an explanation of anything I've noted, please let us know as ther are several folks in this forum who can answer your questions.

 

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region

goatboy's picture

Thanks Kenneth, that's a very thorough explanation! Just one piece to clarify - if the EV storage service restarts while a DA export is running, is the DA export affected?

EV_Ajay's picture

Hi Goatboy,

1. Restarting the EV Services : At the time of DA Export or DA Search usages EV Indexing and EV Storage Services (DLLs). If you restart the EV Services at the time of DA Search / DA Export the search / export will be affected. It means it will try to collect the data from ev server. If EV service restart will take more time than DA search / DA Export timeout or retrycount then those search / export will fail. Otherwise it will work smoothly.

2. Restarting the DA Service : Restarting the DA service (the Enterprise Vault Accelerator Manager Service - a.k.a., EVAMS) pause all running searches and exports to stop until the service is running again. Whenever service is started all pending search and export will start from the point whether they stoped.

Thanks,

Ajay

SOLUTION
Pradeep_Papnai's picture

I don’t think EV services restart necessary for clearing out state MAPI profiles, you can use following registries

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.

Refer TN http://www.symantec.com/docs/TECH68433

Kenneth Adams's picture

Ajay is correct in that restarting the EV Storage Service during an export will cause items attempted to be exported to automatically retry.  If we retry then enough times (5 by default) and fail, we fail those items and the export will have to be retried to retry those items again.

We recommend stopping EVAMS any time the EV Directory,Indexing or Storage service processes are stopped in order to effectively 'pause' any searches, reviews or exports while those services are down. We also recommend stopping EVAMS whenever the SQL Server hosting the DA databases is restarted as the communications channel between the DA and SQL servers would be dropped and not retried after the SQL Server is back online.  This loss of the communications channel causes Event ID 158 errors to be thrown into the DA server's Symantec Enterprise Vault Event Log every 10 minutes for every DA Customer (including Custodian Manager).

 

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region

SOLUTION
EV_Ajay's picture

Hi,

As per mentioned by Ken it's good way to first stop "Enterprise Vault Accelerator Manager" Service and then stop the EV Services will help search to pause effectively.

This will help to decrese chances of failing searches.

 

Thanks,

Ajay

EV_Ajay's picture

Are you having any question that you want clarification, please let us know.

Thanks,

Ajay

EV_Ajay's picture

Hi,

Thanks for marking as solution.

Thanks,

Ajay