#1 Global Leader in Data Protection & Ransomware Recovery

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

KB ID: 2649
Product: Veeam Backup for Microsoft 365
Version: Any
Published: 2018-05-07
Last Modified: 2022-12-09
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.

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.

Purpose

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

Prerequisites

Server Specific

  • The new Veeam Backup for Microsoft 365 server should have the same or newer version of the Microsoft Windows OS.
  • A copy of the Veeam Backup for Microsoft 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 365. The list of supported OS versions is in this article under the OS specification.   
  • Repositories containing data backed up using protected APIs can only be moved between proxies that have protectedAPIs enabled.

Procedure

There are two migration procedures listed below, which one you use will be depend on whether an object storage repository is in use.

Migrate Veeam Backup for Microsoft 365 Server without an Object Storage Repository

  1. Install the same or newer version of the Microsoft Windows OS on the new server.
  2. Install Veeam Backup for Microsoft 365 on the new server.
  3. Stop all the Veeam Backup for Microsoft 365 services on the original server, 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. (Optional) Add a backup proxy from the original site to the new server:
    1. Stop all backup jobs that are running on the proxy.
    2. Open backup job settings and specify to use another proxy.
    3. Remove the proxy from the original Veeam Backup for Microsoft 365 console.
    4. Add the proxy to the new Veeam Backup for Microsoft 365 server.

      Note: Backup proxy server and Veeam Backup for Microsoft 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 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 365 server to verify that you can recover data.

Migrate Veeam Backup for Microsoft 365 Server - with an Object Storage Repository

  1. Before decommissioning the original server, make sure that the backup repository is removed from the configuration.
  2. Build the new server using any supported Windows OS version from the list in this article under the OS specification.
  3. Install Veeam Backup for Microsoft 365 or remotely deploy Veeam Backup for Microsoft 365 proxy 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, 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 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. The created backup repository will be marked as Out of Sync, meaning that the 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 365 server to verify that you can recover data.
Note: Restore points from the original Veeam Backup for Microsoft 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 using the remote proxy.
  2. For each backup job using the remote proxy that will be migrated, open backup job settings and specify to temporarily use a different repository (i.e. Default backup repository).
  3. Remove all local repositories that will be migrated from the Veeam Backup for Microsoft 365 console.
    *If an Object Storage Repository is used by the proxy, follow the steps in the Migration of Veeam Backup for Microsoft 365 with an object storage repository procedure.
  4. (Optional) Remove the original remote proxy from the Veeam Backup for Microsoft 365 console.
  5. Move the repository data from the original proxy to the new proxy.
    *(Skip this step for SMB Repositories)
  6. Add the new remote proxy in the Veeam Backup for Microsoft 365 console.
  7. Add the migrated repository to the new backup proxy.
  8. Edit backup job from Step 2 and reconfigure them to use the repository added from the new proxy location.
  9. Start the original proxy service if it was stopped.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.