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

Retention type changes after re-adding an object storage repository

KB ID: 4176
Product: Veeam Backup for Microsoft Office 365 | 3.0 | 4.0 | 5.0
Published: 2021-05-28
Last Modified: 2021-06-08
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.

Challenge

When a repository extended to object storage that was initially created using PowerShell or REST API is removed from Veeam Backup for Microsoft 365  and then added back, the retention type changes to item-level. This change in retention type after such a repository has been re-added may cause certain items to not be in retention.

This issue applies to versions of Veeam Backup for Microsoft 365 between 3.0 GA (3.0.0.422 ) and 5b cumulative patch KB4135 (5.0.1.225). The currently installed build number can be found in the main menu under Help and Support > About.

Cause

Requirements for Issue to Occur

This issue only affects repositories that meet the following criteria:

  1. Initially created using Veeam Backup for Microsoft 365 3.0.0.422 through 5.0.1.225.
  2. Initially created with REST API or PowerShell.
  3. Configured with the snapshot-based retention.
  4. Extended to object storage
When re-attaching a repository extended to object storage, Veeam Backup for Microsoft 365 reads repository settings from the metadata stored in the cloud. The metadata mistakenly keeps the item-level retention type for repositories that were created initially with PowerShell or REST API and configured with the snapshot-based retention.  

Solution

Install the latest version of Veeam Backup for Microsoft 365 to avoid the issue on existing and new repositories. This issue was initially corrected in build 5.0.1.252.

If any repositories are experiencing this issue, the following steps will allow the repository to be re-added with snapshot-based retention. These steps are to be performed after updating Veeam Backup for Microsoft 365 to version 5.0.1.252 or higher.

  1. Open the Veeam Backup for Microsoft 365 console and stop any active backup jobs.
  2. Open the Services.msc console on the Veeam Backup for Microsoft 365 server.
  3. In the Services.msc console, stop the following Veeam services:
    • Veeam.Archiver.Service
    • Veeam.Archiver.Proxy
    • Veeam.Archiver.RESTful.Service
  4. Copy C:\ProgramData\Veeam\Backup365\Proxy.xml to another location to create a backup of it.
  5. Run Notepad as Administrator and use File > Open to open C:\ProgramData\Veeam\Backup365\Proxy.xml.
  6. Add the following line in the <Archiver> section. If this line already exists, ensure that its value equals True.

    <RepositoryConfig AllowChangeRetentionType="True" />

Example:

<Veeam>
  <Archiver>
    <RepositoryConfig AllowChangeRetentionType="True" />
  </Archiver>
</Veeam>
This configuration change should only be added when working on the issue described in this article.
Do not apply this if a different issue is occurring.
  1. Save the C:\ProgramData\Veeam\Backup365\Proxy.xml file.
  2. Start all the Veeam services.
  3. Re-add needed repositories with the implicitly specified snapshot-based retention using the GUI, PowerShell as described here, or using REST API as described here.
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.