commvault.com commvault.com
Solved

Exchange Mailbox Classic/Journaling Transition to Mailbox V2

  • 10 May 2022
  • 1 reply
  • 705 views
C
Rank
Badge +5
  • Christo Commvault Certified Expert
  • Commvault Certified Expert
  • 5 replies

Hello,

we like to migrate the archive Mailbox Data from Mailbox Classic Agent to the V2 Mailbox Agent - to be able to upgrade from Exchangen 2013 to 2019.
Also a Compliance Mail Journaling Archiving is active.

 

The Documentation is a bit cryptic about that.

https://documentation.commvault.com/11.24/expert/29238_transitioning_to_exchange_mailbox_agent.html

You cannot import content from the Exchange Compliance Archiver Agent or the Exchange Mailbox Archiver Agent directly to the Exchange Mailbox Agent. However, content that was archived using these agents can coexist with the content that is archived using the Exchange Mailbox Agent. The content that you archived using the Exchange Compliance Archiver Agent or the Exchange Mailbox Archiver Agent is available until it is aged based on the retention period that you defined for these agents.

 

This sounds like the old Data is not integratable to the Command Center Console?

 

So we have to implement the Exchange 2019 Journaling newly?

 

https://documentation.commvault.com/11.24/expert/29242_transitioning_from_exchange_mailbox_classic_agent_and_onepass_for_exchange_mailbox_classic.html

  • Only the content from the latest cycle is imported.

This means, all other Cycles from Disk can be deleted? Currently we have copied all Inc and Synthetic Full Archive Jobs from Tape Copies (a former admin created selective copies there and some tapes was deleted due aging problems...) to the Disk location. Since then  all recalls are working.

Now we want to get rid of this many Synfull jobs and reactivate a usable Tape Copy. Or will we run into recall issues with that only last importet cycle?

If so, would we have the idea of dissolving the archive and restoring mailboxes as PST and adding them to Exchange 2019 step by step?

 

https://documentation.commvault.com/11.24/expert/29261_transitioning_from_exchange_compliance_archiver_agent.html

After you transition to the Exchange Mailbox Agent, messages that you archived using the Exchange Compliance Archiver Agent coexist with the content that is archived using the Exchange Mailbox Agent. You can create an Exchange virtual cloud that provides your end users with the ability to search the archived journal messages seamlessly for messages that were content indexed by both the Search Engine and the Exchange Mailbox Agent index server. For more information see, 

 

What does this mean? What is the Exchange Virtual Cloud?

Hopefully someone can help us to understand this process and share his experiences with us.


Thanks a lot.

Christoph

icon

Best answer by Scott Reynolds 10 May 2022, 18:37

View original
If you have a question or comment, please create a topic

1 reply

S
Rank
Userlevel 6
Badge +14

Hello @Christo 

This beginning can be a little confusing but if you drill down to the transaction part it becomes a little more clear.

https://documentation.commvault.com/11.24/expert/29245_preparing_to_transition_to_exchange_mailbox_agent_user_mailbox.html

 

Essentially you will setup the new mailbox agent then run a backup and then one final synethic full backup on the subclients. This gathers all the data and is the “last cycle” SYN fulls the data is carried forward to previous syn full backups are not needed just the last one. 

That data is what is imported in the new agent. You will be able to browse the mailboxes on the new agent and see all the data that was imported from that import operation of that last syn full. Note that last syn full backup should be on disk somewhere as the meta data is imported so the actual data itself is still contained within that job for recalls, restore, etc

This data visible in CommCell console AND Command Center.

That last part is only if you were leveraging Content Indexing with the old agent. If so there is a search cloud that can search for messages from the old agent (old search engine) and the new agent which leverages a different search engine backend.

TLDR:

The important part here is setup the new agent and run a backup of all mailboxes before you import from the old agent. Once that full is complete you can run a inc and once final syn full on the old agent then disable backups. Perform the import operation. Going forward all old and new data is browsable under the new agent for those mailboxes.

Hope this helps clear up some confusion.

Terms & ConditionsCookie settings