#1 Global Leader in Data Protection & Ransomware Recovery

Veeam Backup for Microsoft 365 Backup Copy May Fail to Transfer Microsoft Teams Channel Messages

KB ID: 4436
Product: Veeam Backup for Microsoft 365 | 6.0
Published: 2023-03-28
Last Modified: 2023-03-28
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.

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

Issue Summary

In certain situations, when using a Backup Copy Job with an Archive Appliance to copy data from a Backup Job that was set up solely to protect Teams data via Teams Export APIs, the transfer of Teams channel messages may fail.

 

Requirements for the Issue to Occur

This issue only affects Backup Copy Jobs under the following criteria:

  1. The Backup Copy Job was initially created using one of the following versions:
    • Veeam Backup for Microsoft 365 6a (build 6.1.0.222)
    • Veeam Backup for Microsoft 365 6a P20220825 (build 6.1.0.254)
    • Veeam Backup for Microsoft 365 6a P20220926 (build 6.1.0.423)
  2. Microsoft Graph Export API for Teams is activated;
  3. The Backup Copy Job was created for a Backup Job that only transferred Teams data;
  4. Either Amazon or Azure Archive Appliances are used for backup copy data placement.

 

Issue Detection Script

If you are unsure whether your Backup Copy Jobs are affected by this issue, use the following script to detect affected Backup Copy Jobs and their Repositories.

To use the script, please:

  1. Enable the REST API service;
  2. Download the script;
  3. Modify the script to specify the Veeam Backup for Microsoft 365 server's name and provide account credentials that can be used to connect it.
  4. Run the script, and the output will show you all possibly affected backup copy jobs.
    Note: If a copy job or repository was renamed or deleted, it would not appear in the script output.

 

Should you have any questions, don't hesitate to contact Veeam Technical Support.

 

Solution

If the current Veeam Backup for Microsoft 365 configuration fits the description above, please do the following:

  1. Update to either:
    1. Veeam Backup for Microsoft 365 6a 6.1.0.1015 (P20230322)

      or
    2. Veeam Backup for Microsoft 365 7.0.0.2914 (P20230302)
  2. After the update/upgrade, using the PowerShell cmdlet Start-VBOCopy with the new "-Full" parameter to perform a full sync for Teams backup copy data.

 

Example:

# Specifiy the name of the backup job
$backupJobName = "<job_name>"
# Get the backup job and copy job
$backupJob = Get-VBOJob -Name $backupJobName
$copyJob = Get-VBOCopyJob -BackupJob $backupJob
# Start the Full TeamsData Sync
Start-VBOCopyJob -Job $copyJob -Full -TeamsData
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.