We plan to deploy Exchange 2016. Need to understand what constraints exist with Exchange 2016 with CommVault email archival in its present and future state.
We will stand up two new Exchange 2016 servers and those will be handling all EWS requests. The CDO library is discontinued in 2016 though I believe CommVault only uses 2016. Any requests to a 2010-based mailbox is proxied through a 2010 CAS server. Those 2010 CAS servers are where the current CommVault agents were installed. The existing URLs / DNS entries of webmail.xxxx.local and outlook.xxxx.internal for Exchange 2010 would point to the new Exchange 2016 load balanced IP address, instead of the 2010 load balanced IP address.
So the questions are:
- Can the existing CommVault environment handle going via Exchange 2016 if the agent isn’t installed on 2016 (but remains on 2010)?
- Would CommVault / Exchange be okay if we provided a new URL to access EWS (or whichever protocol) that bypassed the 2016 Client Access Services and instead went direct to the existing Exchange 2010 CAS?
- If a user’s mailbox is still on an Exchange 2010 mailbox, will retrieval continue to work? What about archival?
- If a user’s mailbox has been moved to 2016, will retrieval and archival continue to work?
- Will we need to install the CommVault agent on the Exchange 2016 servers? Is it compatible? Or can we just use it on the Exchange 2010 servers?
Retrieval is critical, ongoing archival is less so. We want to plan moving mailboxes to Exchange 2016 and Online so the behaviour and limitations of CommVault archival and retrieval are key factors in our strategy.