1-800-691-1991 | 9am - 8pm ET

How to Restore from Microsoft Exchange 2007 with Veeam Backup and Replication


This KB article documents the procedure for restoring Exchange 2007 application items using a Surebackup job with export to PST.
Please note that as of April 2017, Microsoft no longer supports Exchange 2007. As such, steps 7 and 8 of this process are no longer supported by Veeam Technical Support.


Please Note: 
  • Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.
1. Create a Virtual Lab.
  • On the proxy tab: Put the production NIC of the Virtual lab on the same network as the Veeam server, and either use DHCP if available in your environment or assign it an unused production IP.
  • On the networking tab: You will want to use "Advanced Single Host".
  • You'll want to configure the internal NIC in the "Network Settings" tab with the same IP address as the production default gateway on the network that the mailbox server and domain controller are connected to.
2. Create an application group.

Add to it the following servers in the order listed here:
     • Domain Controller w/ Global Catalog role
     • Exchange Mailbox server
     • Exchange CAS server (if separate).
Note: In the application group settings, enable the "Domain Controller" role for the DC and remove all test scripts.
For the Exchange server, leave all roles unchecked. Disable the IP boot verification tests on all servers in the application group, and set the application initialization timeout for all servers other than the DC to 0 seconds.

3. Create a Surebackup job.  
Configure it to use the Virtual Lab and Application Group configured in the previous steps.

     • On the Application Group tab, enable the “Keep the application group running once the job completes” option.
     • Do not configure any Linked Jobs

4. Run the Surebackup job.
Note: If you need to restore to a specific restore point choose the “Restore to…” option.

5. Wait for the job to report that all VMs in the SureBackup job are “Started”

6. Ensure Exchange Services are running.
Once the SureBackup job has been run and the required machines are up and running, connect to the CAS server and the Exchange server. Ensure that the Exchange Information Store service (MSExchangeIS) is running.

7. Make sure Outlook is installed on the CAS server.
The export-mailbox cmdlet that will be run later requires it.

8. Launch the Exchange Management Console PowerShell window run the following command to export the desired mailbox as a .pst file
  • export-mailbox –id ‘John Doe’ -PSTFolderPath z:\John.Doe.pst
When the export is finished, you can copy the file via Windows Explorer from the Veeam server by connecting to the CAS server using its masquerade IP (The first octet(s) can be obtained in the “vNIC Connection Settings” on the “Network Settings” page of the Virtual lab settings. The last octet(s) will be the production machine’s last octet(s)).
Common issues:
Make sure that if you are running a 32-bit machine, you download and use the 32-bit Exchange management tools.
If the Exchange restore point is older and the DC is brought up from a newer restore point, the trust relationship might be broken. If this is the case, you’ll need to log into the Exchange server as a local account, remove it from the domain, reboot, re-add it to the domain, reboot again, and from there you may continue with the restore process.

More information

Veeam Backup & Replication
7.x, 8.x, 9.x
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later