Learn How Backup Your Exchange Infrastructure
Learn How Backup Your Exchange Infrastructure
Your Exchange
Infrastructure
Niels Engelen
Systems Engineer for Veeam Software (vExpert, VCP, CCNA)
Johan Huttenga
Solutions Architect for Veeam Software (MCSA, MCITP)
Contents
Executive summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Veeam Backup & Replication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Veeam Backup & Replication for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuring Exchange infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Exchange roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Coexistence with older versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Exchange patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Database Availability Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Mailbox limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Load testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Virtualizing Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuring backup infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Tips for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Performing Instant VM Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Performing item recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Verifying Exchange backups in the Virtual Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Patch testing Exchange in the Virtual Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About Veeam Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Executive summary
This document provides a brief summary of Veeam Backup & Replication (part of Veeam Availability Suite)
and Microsoft Exchange Server. Following a brief discussion of the architecture of both solutions, this white
paper focuses on how to protect and restore Exchange data with Veeam Backup & Replication.
Veeam Backup & Replications architecture allows for high-performing, distributed workloads and is one
of the most powerful solutions for virtual machine (VM) backup, replication and recovery in VMware
vSphere and Microsoft Hyper-V environments.
Exchange 2013s simplified architecturetypically one or several multi-role serversmakes it an ideal
candidate for virtualization. Workload size must be considered, as well as coexistence with older versions and
the layout of the database availability groups that hold email data. However, if planned correctly, virtualization
will improve availability, resource usage efficiency and manageability, ultimately reducing cost. The exact
savings depend on the scenario, but results are typically about 10-50% less power consumption, 10-200%
less administration time and significantly less downtime. When it comes to email servers, even one second of
downtime matters, and this can come at an astronomical price to the business.
The process of deploying Veeam Backup & Replication and setting up Exchange backups is
straightforward; the correct permissions are required for backup and restore, and you must configure
application-awareness to ensure that Exchange is aware that it is being backed up. This uses Microsofts
Volume Shadow Copy Service (VSS), following Microsoft best practices to ensure a consistent state.
After creating the initial backup, it is possible to use it for recovery on a VM level, using Instant VM Recovery
and vPower (patented), which can recover an entire VM in less than two minutes by mounting data directly
over the network from the Veeam server. It is also possible to recover data on an item or mailbox level
using Veeam Explorer for Microsoft Exchange (2010 and later). Backups can also be used to spin up test
environments for backup verification, troubleshooting and patch-testing purposes.
Veeam Backup & Replication significantly simplifies the protection of Microsoft Exchange Server. It
improves availability and uptime through various protection, recovery and testing options. Switching
to Veeam can result in significant cost savings; for example, one security vendor saved over $600,000.
Exchange patching
Because Exchange is a business-critical service and integrates directly with Active Directory (AD),
keeping it up to date is very important, not only to ensure the rollout of bug fixes and updated
functionality, but primarily to maintain good security.
However, upgrading and patching Exchange is not always simple, and installing a cumulative update or
service pack can sometimes failsomething you cannot afford in a production environment.
Make sure that when patching Exchange you first run this as a test, in a test environment that mirrors
production; this way you can extend the AD schema, run the install wizards, fix any issues you might
have and document the entire process before you run this in production.
Virtualizing Exchange
It is crucial that you make Exchange a first-class citizen in your virtual environmentafter all, it is running one
of the most mission-critical workloads in your infrastructure. With the current Exchange architecture, it is easily
virtualized, and this comes with benefits around high availability, resource usage efficiency and management
flexibility, all of which will result in cost savings. Of course the exact savings vary for each deployment, but
calculating the ROI should not be hard. The numbers vary, but typically virtualization results in 10-50% less
power consumption, 10-200% less administration time1 and significant reductions in downtime. Every second
an email server is unavailable is critical; downtime of an hour is generally unacceptable. Extended downtime
can come at an astronomical price to the business.
It is a good idea to review the detailed VMware and Microsoft best practice documentation
concerning the virtualization of Exchange, and even though some of the documentation is a little
dated, a lot of it is still relevant today. Also make use of the Exchange sizing calculator to ensure that
you allocate the correct amount of resources to each component.
1. Figures based in part on VMware data provided by EMA and Cisco customer data.
10
11
This will start a restore wizard to quickly recover the full VM. First select the backup job that contains the
VM or use the search option.
In the Restore Point tab, select the point you wish to restore to. Then choose the Restore Mode.
12
Select Restore to the original location if you want to restore VM and the original is lost; do not choose
this if the original VM is still available in your infrastructure. This will restore the VM with its original
settings, to its original location. If this option is selected, you will pass directly to the Restore Reason
step of the wizard. This will re-use settings, such as the original host, resource pool and folder, which
were saved in the backup file. Select Restore to a new location, or with different settings if you want
to restore VMs to a different location and/or with different settings (such as VM location, network
settings, the format of restored virtual disks and so on). If this option is selected, the Instant VM
Recovery wizard will include additional steps to allow for customization.
In the Restore Reason step you can specify a reason for restore (this is not required, but it allows for
auditing), which will lead to the Ready to Apply step where Veeam offers two extra options.
You can select Connect VM to network and Power on VM automatically so that the server becomes
available as soon as the recovery is done.
NOTE: The user interface for an Instant VM Recovery on VMware (shown in this guide) and Hyper-V differ
slightly; however the general options available are the same.
Veeam will now perform the recovery based on the instructions given, exposing an NFS datastore for
VMware or using a filter driver for Hyper-V to run the VM from the backup file and power it on so you
can use it again. Finally, Veeam can migrate this server back to production using either the virtualization
platform tools (Storage vMotion or Live Migration) or Veeam's Quick Migration (VMware only).
13
This time select Application items under the Restore from backup list.
14
In the next step you will be able to select Microsoft Exchange as the application.
This will start the Microsoft Exchange Item Level Restore wizard.
15
Now select the correct Exchange Server and then select the Restore Point. A reason can be defined in the
Restore Reason step (for auditing) and when ready, Veeam Explorer for Microsoft Exchange will start.
Once started, you can browse the Exchange database, search for and find the items you wish to restore,
such as email, calendar items or tasks.
NOTE: Veeam Backup & Replication v8 adds support for restore of permanently deleted items and Online Archive
mailboxes. For more information about this and other features, have a look at the Whats New document.
16
After this you can right-click the item or mailbox you wish to restore and select the appropriate option.
17
By following the step-by-step instructions presented in the user guide, you can configure a Virtual Lab
and get started with automatic testing by using SureBackup.
18
By enabling this option you will be able to log on to the servers by using the virtual console via the vSphere
Web Client or the Hyper-V Manager and run whatever tests and additional commands are required.
Virtual Lab access can be delegated, and because of its usefulness in testing, it can lead to massive
organizational savingsfrom streamlining change control to speeding up product development lifecycles.
NOTE: Remember that your changes are not saved after you are finished testing, so be sure to document the
process, after which you can apply your changes in production. Although it is possible to migrate a VM from
inside the Virtual Lab back to production in VMware by cloning the VM or using a Veeam VM copy job, it is not
a good idea to do this with Exchange, as it must remain running at all times (where possible).
19
20
21