Email Exchange 2019 not working

Hello Sachin Ingale
Thank you for posting question to Microsoft Q&A Forum.
Based on my research, this issue happens because Exchange does not store its full configuration locally on the server. Most of the Exchange configuration is stored in Active Directory, so restoring a full VM image can leave the Exchange server and Active Directory in an inconsistent state. As a result, services may fail to start properly, databases may not mount, or client access features such as OWA and ECP may not work as expected.
Could you check on the answers given by Q&A Assist below to see if it could help?
I also sent a private message to you in case you would like to share more details along with me with possible screenshots.

I am looking forward to your reply.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

After restoring an Exchange Server 2019 VM or system from a Veeam backup, Exchange can start but not function correctly because Exchange is tightly integrated with Active Directory and its configuration is stored there, not just on the server. A full image restore can leave the server in an inconsistent state.

Use the supported recovery approach for Exchange instead of relying only on a VM restore:

1. Verify Active Directory and DNS
   • Ensure the domain controllers and DNS are healthy and reachable.
   • Confirm the Exchange server’s computer account still exists and matches the restored server (name, IP, etc.).
2. Prefer Exchange Server Recovery (/m:RecoverServer)
   • If the original server is lost or the restored one is unstable, rebuild the OS with the same computer name and join it to the domain.
   • Run Exchange Setup with the /m:RecoverServer switch to recover the server configuration from Active Directory:
     • This re-creates the Exchange roles and configuration stored in AD.
   • Be aware that local changes such as custom web.config edits and custom registry entries are not restored and must be reapplied manually.
3. If databases were restored from backup
   • If Veeam restored mailbox databases, ensure they are in a clean shutdown state before mounting. If they are in dirty shutdown when restored to an alternate location, use Eseutil to bring them to clean shutdown as required.
   • If using Windows Server Backup or another VSS-based backup, follow the supported restore process and, when restoring to an alternate location (for a recovery database), manually bring the database to clean shutdown before mounting.
4. Recover databases and mailboxes if needed
   • If databases are corrupted or missing, recover them from backup using a supported method (for example, DPM or VSS-based backup) and mount them.
   • For mailbox-level recovery, use a recovery database and New-MailboxRestoreRequest as documented. Ensure the server is on a supported cumulative update so mailbox restore cmdlets function correctly.
5. Ensure Exchange 2019 is on a current Cumulative Update
   • Several recovery and restore issues (including New-MailboxRestoreRequest failures and RecoverServer problems) are fixed in later CUs. Install the latest CU for Exchange 2019 to avoid known issues with recovery operations.

If the restored server remains unstable after these checks, the recommended path is:

• Build a new Exchange 2019 server with the same name and use /m:RecoverServer to recover it from AD, then
• Attach or restore databases using a supported backup/restore method.

References:

• Backup, restore, and disaster recovery in Exchange Server
• Restore a backup of Exchange using Windows Server Backup
• Back up Exchange with DPM
• Connect-Mailbox and New-MailboxRestoreRequest cmdlets fail in Exchange 2019 and 2016 (KB5012783)
• RecoverServer operation fails in Exchange Server 2019
• Cumulative Update 12 for Exchange Server 2019 (KB5011156)
• "Could not start MS Exchange Service Host service" error and Exchange stops responding
• Start-MailboxAssistant is not available in Exchange Server 2019 (KB5012758)