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

How to move Veeam Backup for Microsoft Office 365 to a new server

KB ID: 2649
Product: Veeam Backup for Microsoft Office 365
Version: Any
Published: 2018-05-07
Last Modified: 2021-06-10

Objective

This article documents the procedure for moving resources assigned to a Veeam Backup for Microsoft Office 365 server installation to a new Veeam Backup for Microsoft Office 365 server.
At the time of writing this article, there is no way to export the configuration of Veeam Backup for Microsoft Office 365. As such, on the new server, all organizations and jobs will have to be recreated. If the steps below are performed correctly, the first run on the new server will be "incremental."

Prerequisites

Server Specific

  • The new Veeam Backup for Microsoft Office 365 server should have the same or newer version of the Microsoft Windows OS.
  • A copy of the Veeam Backup for Microsoft Office 365 license will be needed during installation.

Repository Specific Considerations

  • If the existing backup repository is a network share, the new server must have access to that share.
  • If the existing backup repository is an iSCSI drive,  it must be disconnected from the original server first (to avoid the two iSCSI initiators issue), then connect the iSCSI drive to the new server.
  • If the backup repository is object storage, then the new server can have any Windows OS version supported by Veeam Backup for Microsoft Office 365. The list of supported OS versions is in this article under the OS specification.   

Procedure

The procedure for migrating Veeam Backup for Microsoft Office 365 differs depending on whether an object storage repository is in use.

Veeam Backup for Microsoft Office 365 server migration:

  1. Install the same or newer version of the Microsoft Windows OS on the new server.
  2. Install Veeam Backup for Microsoft Office 365 on the new server.
  3. Stop all the Veeam Backup for Microsoft Office 365 services on the original site before moving any data.
  4. Copy the backup repository data to the backup repository location on the new server.
  5. Add the same Microsoft Office 365 organization on the new server.
  6. Add a backup proxy from the original site to the new server (optional):
    a. Stop all backup jobs that are running on the proxy.
    b. Open backup job settings and specify to use another proxy.
    c. Remove the proxy from the original Veeam Backup for Microsoft Office 365 console.
    d. Add the proxy to the new Veeam Backup for Microsoft Office 365 server.
    Note: Backup proxy server and Veeam Backup for Microsoft Office 365 server must be deployed within the same domain or within trusted domains.
  7. Add the backup repository (from a new location).
  8. Restore Points created on the original Veeam Backup for Microsoft Office 365 server can be accessed by right-clicking the corresponding organization.
  9. Run a test restore from the organization using a restore point created on the original Veeam Backup for Microsoft Office 365 server to verify that you can recover data.

Migration of Veeam Backup for Microsoft Office 365 with an object storage repository:

  1. Prior to decommissioning the original server, make sure that the backup repository is removed from the configuration.
  2. Install any supported Windows OS version from the list in this article under the OS specification on the new server.
  3. Install Veeam Backup for Microsoft Office 365 on the new server.
  4. Add the same storage account to the new server.
  5. If you see the “Cannot override repository ownership because the object storage repository is locked” message and you no longer have access to the original server, then navigate to the corresponding bucket/container and delete the object inside the RepositoryLock folder.
    Refer to this article for information on the structure of the Veeam Backup for Microsoft Office 365 object storage repository and how to locate the RepositoryLock folder.
  6. Create a new backup repository and extend it with the needed storage account.
  7. Created backup repository will be marked as Out of Sync meaning that metadata needs to be synchronized from the bucket/container to the persistent cache folder on a local disk.
    Click Yes to start synchronization immediately.
    Alternatively, the persistent cache folder can be synchronized manually as described in this article.
  8. Add the same Microsoft Office 365 organization to the new server.
  9. Run a test restore from the organization using a restore point created on the original Veeam Backup for Microsoft Office 365 server to verify that you can recover data.
Note: Restore points from the original Veeam Backup for Microsoft Office 365 server are available as soon as the organization is added to the console.

More information

Migration of a remote proxy to another host (optional):

  1. Stop all backup jobs that are running on a remote proxy.
  2. Open backup job settings and specify to use a different proxy.
  3. In case an object storage repository is used by this proxy, follow the steps of the Migration of Veeam Backup for Microsoft Office 365 with an object storage repository procedure.
  4. Remove the original remote proxy from the Veeam Backup for Microsoft Office 365 console.
  5. Move the repository data from the original proxy to the new proxy where the new repository is planned. For example, using RoboCopy.
  6. Add the new remote proxy in the Veeam Backup for Microsoft Office 365 console.
  7. Add an old repository from the new proxy location.
  8. Edit backup job settings so that backup jobs use the repository added from the new proxy location.
  9. Add the new remote proxy in the Veeam Backup for Microsoft Office 365 console.
  10. Add a new repository (specifying the path from step 4) that is associated with the new remote proxy.
  11. Open backup job settings and specify to use the new remote proxy if needed.
KB ID: 2649
Product: Veeam Backup for Microsoft Office 365
Version: Any
Published: 2018-05-07
Last Modified: 2021-06-10

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.