MS Exchange 2016 VMs & Database Backup Job best Practices

[samed]

Dear Team,

One of our customer recently installed Veeam Backup & Replication 9.5 for exchange server backup.
Customer have MS Exchange 2016 (2 servers) configured as DAG (Database Availability Group) for DB Redundancy.

We need to know what is the best practices for Exchange 2016 Backup Jobs (for VMs & DB backup & Restoration).


Exchange Server Details:
OS: Windows server 2012R2
MS Exchange 2016 Standard

VMWare Esxi 6.5

[foggy]

Hi Abdussamed, please review this thread and the best practices document as well and feel free to ask any additional questions.

[samed]

Thnanks.

[lance.hammond]

Looking for feedback.

Currently we have a physical deployment of Exchange 2010 configured in a DAG across two sites. If one site drops connection to the outside world, email is able to start flowing from the other site.

Goal - Ability for Exchange to failover between two sites (NO DOWNTIME) & granular restoration options

How granular can Veeam get with restorations, down to specific user mailbox?

We are entertaining the idea of virutalizing Exchange and moving to 2016.

The question is does it still make sense to configure a DAG?
Is there a recommended way to acheive our goal by utilizing Veeam that may provide more advantages than a DAG?

Thanks for any insight.

[PTide]

Hi Lance and welcome to the community!

How granular can Veeam get with restorations, down to specific user mailbox?

Yes, down to mail, calendar, contacts.

Is there a recommended way to achieve our goal by utilizing Veeam that may provide more advantages than a DAG?

You can combine both, actually. Aside of useful resources already mentioned by foggy, this whitepaper is also worth checking.

Thanks

[lance.hammond]

Thank you, I will check out that information.