#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

Repository upgrade error: "Some of the data in this repository is incompatible with the immutability settings."

KB ID: 4644
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-10-10
Last Modified: 2024-10-10
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our 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

error icon

Oops! Something went wrong.

Please, try again later.

Solution Requires Data Deletion

The resolution procedure of this article involves the directed deletion of backup data that should not have been migrated to the immutable repository.

Please review all details of the article closely, and contact Veeam Support if you would like assistance.

Challenge

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.

Cause

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.

Solution

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.

To resolve this issue, the backup data migrated to the immutable object storage must be removed to allow the repository to be upgraded after the upgrade to Veeam Backup for Microsoft 365 v8.

Consider the following:

  • Backup data that was mistakenly migrated to the immutable repository cannot be moved to another repository.
  • The precheck scripts provided below can be used prior to upgrading Veeam Backup for Microsoft 365 to version 8. This can help determine whether a deployment is impacted by this issue. If impacted, appropriate plans should be made to ensure that all backup jobs are configured to use the supported repository types.

Requirements

The scripts in this section require:

  • AWS CLI or Azure CLI must be installed, depending on which type of object storage is in use.
  • PowerShell 7
  • For Azure storage, the Azure CLI extension 'storage-blob-preview' is required: 
    • az extension add --name storage-blob-preview

Prepare the Environment

  1. Ensure all jobs and restore tasks are stopped.
  2. Reconfigure all jobs targeting the repository that cannot be upgraded to use a different repository.
    Note: Please don't run the jobs after changing which repository they use; only change the repository they target so that the repository can be removed. Create a temporary repository to assign the jobs to if one is not available.
  3. Remove the problematic repository from Veeam Backup for Microsoft 365.

Check if the Repository is Impacted by the Issue

  1. Download the precheck script for the object storage vendor used by the Repository.
  2. Review the command examples below and specify the parameters as shown.
.\AWSCLI_PRECHECK.ps1 -AWS_ACCESS_KEY_ID "your-access-key-id" -AWS_SECRET_ACCESS_KEY "your-secret-access-key" -Region "us-east-1" -Bucket "your-bucket-name" -FolderPaths "path" -Endpoint "https://s3.amazonaws.com"
.\AZURECLI_PRECHECK.ps1 -Storage_Account_Name "your_account_name" -Storage_Account_Key "your_account_key" -Container_Name "your_container_name" -FolderPaths "path"
Data Deletion
The backup data that should not have been migrated to the immutable repository must be removed to upgrade the immutable repository. The scripts in the next section will delete that backup data.

Remove the Detected Invalid Backup Data

  1. If the script reports "Found corrupted repository", download the script below that matches the object storage platform to remove those discovered objects/blobs.
  2. Review the command examples below and specify the parameters as shown.
.\AWSCLI_REMOVE_OBJECTS.ps1 -AWS_ACCESS_KEY_ID "your-access-key-id" -AWS_SECRET_ACCESS_KEY "your-secret-access-key" -Region "us-east-1" -Bucket "your-bucket-name" -FolderPaths "path" -Endpoint "https://s3.amazonaws.com"
.\AZURECLI_REMOVE_BLOBS.ps1 -Storage_Account_Name "your_account_name" -Storage_Account_Key "your_account_key" -Container_Name "your_container_name" -FolderPaths "path"

Re-add the Repository and Finalize

  1. Re-add the repository to Veeam Backup for Microsoft 365.
  2. Upgrade the repository.
  3. Re-configure all jobs modified in Step 3 to use the now repaired and upgraded repository.

Download Information

Read Entire Article Closely
Read all instructions carefully before executing any of the provided scripts.
DOWNLOAD SCRIPTS

Updated: 2024-08-03

MD5: F1FB1099D5435BFFF5BF66731E568DAA
SHA1: 8B1A5ED64F4479D64DC69CA468503C48D2243CE4

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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.