Three Ways To Restore Exchange Servers With Datto SIRIS

Jan 27, 2017

Three Ways To Restore Exchange Servers With Datto SIRIS

BY Henry Washburn

BCDR Datto Products

Backing up Exchange Server is critical for business continuity. People lose emails, drives fail, and servers can be compromised. Below are three efficient ways that Exchange servers can be recovered (running on a Datto SIRIS after a disaster), and then restored back to a production server (returning normal operations). Of course, if you have migrated to Exchange O365, you don’t have to deal with this whole process, because you should have Backupify for O365.

Scenario 1: The physical Exchange server’s backplane failed, and it’s going to take three days before new parts arrive.

  1. Recovery - This is an easy one...locally virtualize and then backup the local virtualization back to the SIRIS.

  2. Restore - Unless there is some other terrible stuff on the server.

  1. Schedule maintenance time for this...not entirely necessary, but there would be a short email outage.

  2. Find a machine with Outlook that works with your Exchange Server.

  3. Install Kroll Ontrack Powercontrols onto that workstation (comes free with all SIRIS devices).

  4. Take one last backup of the VM running on the SIRIS.

  5. Start a file restore with the SIRIS.

  6. Power down the VM.

  7. Power on the server after it is repaired make it live on the network.

  8. Run Powercontrols on the Outlook machine.

  9. Select the two Exchange Database (EDB) files (One from the file restore via SAMBA and the other from the old Exchange Server.

  10. Let Kroll check both for differences.

  11. Import those differences to the old Exchange EDB.

  12. Restore Complete.

Scenario 2: Virtual exchange server crashes (using VMware).

  1. Recovery - Virtualize via ESX
    This type of restore adds the a restore datastore from the Datto device to the VMware server so you can use the hypervisor’s CPU and RAM.

  2. Restore - Even simpler than scenario 1.

Option 1: Full Storage vMotion back to a datastore of your choice.

Option 2: Use VMware Converter Standalone to convert a VMDK restore from the Datto device to your hypervisor, in any format you like.

Scenario 3: The VMware cluster went down, and there is no VMware High Availability...bigger than JUST a local virtualization. To reduce scope I will just talk about the Exchange Server restore.

  1. Recovery - In an actual disaster recovery that requires offsite virtualizations, contact support for assistance and Datto will help provide the best and fastest solution to recover and then restore.

    1. Go to the partner portal and virtualize your Windows Domain server

    2. Batch virtualize the other VMs as needed.

      1. Change your MX records as needed.

      2. Have you users connect via VPN, RDP or IPSec.

  1. Restore - I am only talking about Exchange here because there are many options.

    1. Have Datto Support send an incremental snapshot down to the Datto device.

    2. Use Kroll Ontrack (like in the first instance) to compare the current EDB against the old EDB and have Kroll update the old EDB with all the new emails/contacts/calendar info, etc.

This list is by no means the definitive list of possible restores users can perform with a Datto device. In fact, your DRaaS solution should be flexible enough to handle a wide variety of potential disasters. Your solution should be a tool that you can manipulate in any way that you need. If you have other ways you have restored (or failed at restoring) data using any solution, let me know! Message me on Twitter or LinkedIn, I would love to discuss how it worked and if there were more efficient ways of restoring.

Subscribe to the Blog