Do Archiving Tasks Stop working whilst mailbox is migrated

[Ravi_Bhandari]

Sorry for the silly question, but I have noticed that both my exchange 2010 and 2013 archiving tasks have stopped processing mailboxes during our current migration to Exchange 2013.

The archiving task schedule hasn't changed, and when I look for the archived mail reports the following morning there are none present.

The only thing I can find in the event viewer are numerous entries such as;

Abnormal error occurred

Event Id 6592

Task Category: Migrator Server

Reference: CStore::CurrentVault()/Vault object is null

Is this expected behaviour?

I have EV 10.0.4 running on windows 2008R2.

Everything was working fine until about 3 days ago and this was whilst the migrations were already taking place.

[JesusWept3 · Accepted solution]

Are you targeting both the source and the target exchange servers?
The system mailbox that the EV Archiving Task uses on Exchange 2010, does it still reside on an 2010 server?

Because what might have happened is you may have an archiving task for ex2010Server.myDomain.com but you moved it to ex2013Server.myDomain.com, and then when the task attempts to connect to it, it can't find the system mailbox and thus the connection fails.

Is the Exchange 2013 implementation entirely seperate? or is it set to work in mixed mode, so that Exchange 2010 and 2013 can co-existance until you've gotten rid of all your 2010 servers? or is it an entire new Exchange environment in 2013?

If it's a new environment, have you run the permissions and throttling scripts for the EVAdmin for 2013?

If it's a mixed environment, what version of Enterprise Vault are you running? because you would need EV10 SP4 CHF3

http://www.symantec.com/business/support/index?page=content&id=TECH209191