Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
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.
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.
Veeam Backup for Microsoft 365 v8 Prepare New Server Install Veeam Backup for Microsoft 365 on the new server and add remote proxies (if needed). Add the same Microsoft 365 organization on the new server. Add the same Object Storage account to the new server. Migrate Data From Old Server Delete backup jobs and copy jobs or set them to a different target repository. Make sure that the backup repository is removed from the configuration. (Optional) To migrate local backup storage, copy the backup repository data to the backup repository location on the new server. Complete Migration on New Server Add the backup repository(s). (For OSR only) If you see the “Cannot override repository ownership because the object storage repository is locked” message and you can no longer access 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. (For OSR only) 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. Click Yes to start synchronization immediately. Alternatively, the persistent cache folder can be synchronized manually, as described in this article. Restore Points created on the original Veeam Backup for Microsoft 365 server can be accessed by right-clicking the corresponding organization. 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.