Loading...
Loading...
After upgrading to Veeam Backup for Microsoft 365 v8, attempting to upgrade an immutable repository fails with the error: Cannot upgrade this repository (ID: <guid>). Some of the data in this repository is incompatible with the immutability settings. For more details, see KB4644.
This error occurs because data that may have been mistakenly transferred to that repository using Move-VBOEnttityData was detected. Under certain conditions, it was possible in Veeam Backup for Microsoft 365 v7(a) to transfer backup job data to an immutable repository that should not have been transferred, as technically, only backup copy job data should be stored on an immutable repository. This limitation was detailed in the Release Notes as a known issue: Using the Move-VBOEntityData cmdlet, you can move backup data to an immutable object storage repository. After such a move only backup copy jobs can be configured to the target repository containing the migrated backup data. Regular backups to an immutable object storage are unsupported. Because this backup data is not expected to be present in the repository (which was only intended for storing backup copies), after upgrading to Veeam Backup for Microsoft 365 v8, the software cannot upgrade such a repository correctly. As documented in KB3067, the migration of backup data from a JET-based backup repository to immutable object storage using Move-VBOEntityData is not supported.
Support Assistance Available This procedure was written to provide customers with a self-service solution to this issue. However, we understand that this procedure can be daunting as it involves deleting backup data. If you need help, please create a support case and reference KB4644.
Read Entire Article Closely Read all instructions carefully before executing any of the provided scripts.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.