Rapid Recovery

Exchange 2016

Hello, we are using the latest build (, but it seems that Exchange 2016 is not currently officially supported.

Has someone tested the compatibility with Exchange 2016, or when will it be offically supported?


  • AppAssure does not support Exchange 2016 for mountability or checksum checks.  It also does not support granular restore of Exchange data.  You should be able to back up the Exchange volumes no different than any other Exchange server and get consistent backups, the tools for working with that data simply aren't compatible with it yet.  We have not tested with log truncation either.  

    Official Exchange 2016 support is coming in a future build.  We do not have an ETA for Exchange 2016 support at this time.

  • In addition to Tim's response regarding Log Truncation, please read the information below regarding CRCL (Continous Replication Circular Logging) which was introduced in Exchange 2013, as described on Technet (technet.microsoft.com/.../dd876874%28v=exchg.150%29.aspx;MSPPError=-2147217396). It applies to DAG environments and is performed by the Replication Service:

    One of the functions performed at the end of a successful full or incremental backup is the truncation of transaction log files that are no longer needed for database recovery. If backups aren't being taken, log truncation won't occur. To prevent a buildup of log files, you enable circular logging for your replicated databases. When you combine circular logging with continuous replication, you have a new type of circular logging called continuous replication circular logging (CRCL), which is different from Extensible Storage Engine (ESE) circular logging. Whereas ESE circular logging is performed and managed by the Microsoft Exchange Information Store service, CRCL is performed and managed by the Microsoft Exchange Replication service. When enabled, ESE circular logging doesn't generate additional log files and instead overwrites the current log file when needed. However, in a continuous replication environment, log files are needed for log shipping and replay. As a result, when you enable CRCL, the current log file isn't overwritten and closed log files are generated for the log shipping and replay process.

    Specifically, the Microsoft Exchange Replication service manages CRCL so that log continuity is maintained and logs aren't deleted if they're still needed for replication. The Microsoft Exchange Replication service and the Microsoft Exchange Information Store service communicate by using remote procedure calls (RPCs) regarding which log files can be deleted.

    For truncation to occur on highly available (non-lagged) mailbox database copies, the following must be true:

    •The log file has been backed up, or CRCL is enabled.

    •The log file is below the checkpoint.

    •The other non-lagged copies of the database agree with deletion.

    •The log file has been inspected by all lagged copies of the database.

    For truncation to occur on lagged database copies, the following must be true:

    •The log file is below the checkpoint.

    •The log file is older than ReplayLagTime + TruncationLagTime.

    •The log file is deleted on the active copy of the database.

    Another option to perform log truncation is setting up Disk Shadow to perform it right after a successful snapshot. This would be based on the capability of the AppAssure agent to execute a powershell script right before and after taking a snapshot. Since diskshadow accepts a file with commnds as input, it is easily doable (albeit not necessarily recommended. Basically you need 2 things:

    1. Write a script (support.software.dell.com/.../119429) that self-checks it has been run already during a 24 hours time interval

    2. Include Diskshadow.exe running at a minimum the following commands (you need to check this as I quote them from memory; hope that it is ok, though)

    set context volatile

    add volume <volume_name>:

    begin backup


    end backup

    Just found a KB support.software.dell.com/.../122647 that kind of validates what I have written above (setting the context is not mentioned although I believe it is necessary).

    Hope that helps if you have to protect Exchange 2016 using AppAssure while waiting to be fully supported.

  • Hi,

    Exchange 2016 support is planned for a release later this year.

  • Hi Roger,  Any update on 5.4.x support on Exchange 2016 or RR6 is the only way to go?

  • So, it`s been awhile and there has been no updated about the plans to support Exchange 2016, we are currently looking at rolling out Exchange 2016, But are waiting to see when Rapid Recovery will support Exchange 2016 backups.  Can we please get an ETA, do i need to ask Santa :)