#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

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

KB ID: 2303
Product: Veeam Backup & Replication
Version: 7.x, 8.x, 9.x
Published: 2017-06-15
Last Modified: 2020-08-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

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.

Solution

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.
http://helpcenter.veeam.com/backup/80/vsphere/appgroup_create.html

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.
Note:
     • 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.
https://www.microsoft.com/en-us/download/details.aspx?id=11876
 
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

Reference KB’s
 
https://www.veeam.com/kb2047
 
https://www.veeam.com/kb2059
 
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.