Starting/stopping maintenance mode in large Exchange 2010 deployment

We noticed that StartDAGServerMaintenance.ps1 -serverName SERVER is not working well for large deployments - causes indexes corruption. 

Before putting server in the maintenance, databases should be moved manually or using your favorite Powershell script) out of the server.

After that SERVER can be put into the maintenance node with no problems.

Enterprise Vault - SQL Query to find number of items awaiting indexing

SELECT Count(*) FROM JournalArchive WHERE IndexCommited = '0'

 

Note: it should be ran on the Vault Database