Exchange SE version

Support for Exchange SE is expected to be supported for 11.40 in Sept software release.

We are also evaluating backporting support but that is still TBD. I would not expect any backport to 32 most likely 36.

Thanks

Hi, ​@Scott Reynolds 

The customer has Exchange 2019, for which support ends on October 14, 2025. An upgrade from Exchange 2019 to Exchange SE, specifically to version 15.02.2562.017, is planned.

The environment is currently working on version 11.32 (long-term support) with support until 15 June 2026. Why wouldn't support for Exchange SE cover this version? I would appreciate it if you could consider the backport.

https://documentation.commvault.com/11.40/software/commvault_software_releases_release_types_and_release_tracks.html

Hello ​@Michal Osewski ​@Roberto Durso 

Thanks yes, we are looking into this, but this is still under review.

Documentation will be updated but there is no specific ETA at this time.

I will update this thread once everything is confirmed.

Just ran into this issue with a customer too - They’ve just upgraded from 11.32 to 11.36.72.  They are able to backup the individual Exchange Servers, but not setup the DAG.  It detects the Member servers, but they’re greyed out and can’t be selected.

I’m hoping they will backport to 11.36 to add support?

Hello ​@Stuart Walker  Was there a case opened for that issue?

Can you share TR number if possible?

If on the latest service pack, I do not believe we expect any issues.

Hi ​@Scott Reynolds,  

I don't see any information about Exchange Server SE support for version 11.32. When can this information be expected in the documentation?

https://documentation.commvault.com/2023e/commcell-console/system_requirements_for_exchange_database_agent_02.html

We didn’t create a ticket, but we will be, today or tomorrow.  Lots of other little issues to chase up.
They’re on 11.36.72

The exchange servers have Exchange Agent and the Exchange Database client, and have been used for Exchange Database backups directly to the server(s), as they were originally stand alone.  THey have since changed them to a DAG.  When create a DAG pseudoclient, it detects the members, but they’re not selectable.

Ticket 250924-229 created

Confirming the case is closed. Hostname of VM did not match.