Knowledge Base Listing Page
How to migrate backup data between repositories for Veeam Backup for Microsoft Office 365

How to migrate backup data between repositories for Veeam Backup for Microsoft Office 365

KB ID:	3067
Product:	Veeam Backup for Microsoft Office 365 \| 5.0
Published:	2019-12-16
Last Modified:	2021-10-27

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's 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

Oops! Something went wrong.

Please try again later.

Purpose

This article provides information regarding migrating backup data between local repositories and from a local repository to an object storage repository when using Veeam Backup for Microsoft Office 365.

Note: Data can only be migrated using PowerShell cmdlets.

This article documents how to migrate backup data between repositories. For details on how to move the Veeam Backup for Microsoft Office 365 installation to a new server, please review: https://www.veeam.com/kb2649

Solution

The Move-VBOEntityData PowerShell cmdlet is used to move backup data from one repository to another repository.

Limitations and Considerations of the Move-VBOEntityData cmdlet:

Move-VBOEntityData supports the following data migration scenarios:
- Migration from one local backup repository to another local repository
- Migration from a local backup repository to an object storage repository
The following migration scenarios are not supported:
- Migration from an object storage repository to another object storage repository.
- Migration from an object storage repository to a local repository.
Restore points that are migrated will no longer be attached to the original job. The restore points are still available for restore and can be accessed by right-clicking on the corresponding organization name.
The Move-VBOEntityData cmdlet will not reconfigure backup jobs to change the repository they use. The jobs must be reconfigured manually or by using additional PowerShell cmdlets (as is done in the script example found in this article).
It is recommended to run migration operations outside of backup windows to avoid overhead on a proxy and affecting backup jobs performance.

More details...

Usage examples for the Move-VBOEntityData cmdlet

Examples are available in the PowerShell Reference guide here: Move-VBOEntityData - Examples

Monitoring the Move-VBOEntityData migration progress

Status of migration tasks is displayed in the Veeam Backup for Microsoft Office 365 Console in the History tab under the Job > Data Management node.

Migration Script Example

The script below is designed to automate backup data migration between repositories.

Expand to learn more about how this script works

The script performs the following operations:

Select Organization. Defines the organization associated with the data to be migrated.
Select Backup Proxy. Defines the backup proxy server that hosts existing backup data.
Select Target Repository. Defines the target object storage repository.
Limit Migrations Sessions. This step configures the maximum number of simultaneous migration sessions to half of all threads configured for the selected backup proxy server. For example, if there are 64 threads configured on the backup proxy server, it will limit the number of migration sessions to 32 concurrent migration sessions.
Disable All Jobs for Selected Organization. Disables all backup jobs created for the specified organization.
Create a List of Source Repositories. Creates a list of backup repositories used by the backup jobs from Step 5 that will be used as source repositories. (If a repository is not in use by at least one backup job, the data residing there will not be migrated.)
Get and Migrate All Users. Creates a list of all Users, Sites, Teams, and Groups located in the repositories from Step 6 and then migrates their data.
Reconfigure Jobs to Use New Repository. Reconfigures all the jobs from Step 5 to use the object storage repository that is defined as a target repository and enables all jobs disabled at Step 5.

To run the script, download the file below, place it on the Veeam Backup for Microsoft Office 365 server. Then, run the "kb3067.ps1" file and follow the script prompts.

DOWNLOAD SCRIPT

This script was written for use with Veeam Backup for Microsoft Office 365 5B or later.

For ease of use, comments are provided for each step in the script.

MD5: F286D3FB73FA0880EEB077B294122256
SHA-1: 85007CA887E9F2066E169307BCAFFAA42A2F5250

Support Statement

This script is provided as a courtesy and is not supported by Veeam Technical Support. Use at your own risk.

Veeam Technical Support will not assist in the usage or troubleshooting of this tool.

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

E-Mail

Product

Topic

Description

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:

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!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.