Skip to main content
  • EN

Hi there,

currently i’m migrating a customers Veeam Backup for Microsoft 365 from local disk Storage to S3 (Wasabi). Doing this via the Script method from KB3067: How to Migrate Backup Data Between Repositories for Veeam Backup for Microsoft 365 and this works for me pretty well on another customers environment in the past.

 

On the actual customers environment, i get Warnings regarding the Users Achive Mailbox:

09.10.2024 07:08:36 :: Moving archive mailbox USERNAME completed with warning: archive mailbox USERNAME is not found in repository

I have the info from my colleague, that this customer has no active archive function on many users (not all), so the warning is for sure correct.
But as it’s currently in migration phase and not yet completed (will take a few days), i’m not sure if this will end up with problems after the migration (i.e. in a restore)? For sure, we will test some restores (with focus on those users with warnings).

The script from KB3067 is not in support by Support, so contacting them, shouldn’t be an option.

Does anyone have some experience here? 

Thanks and best regards
Markus

Have not run this script for migrations but based on the warning you should be fine.  Only testing after migration will tell you.  Best of luck.

Hi,

I checked the PowerShell script and I can confirm this is a valid warning but nothing you need to worry about.
 

foreach ($user in $users)
{
    Write-Host $user.displayname
    Move-VBOEntityData -From $fromRepo -To $destinationRepo -User $user -Mailbox -ArchiveMailbox -OneDrive -Sites -Confirm:$false -RunAsync
    while((Get-VBODataManagementSession | ? {$_.Status -eq "Running"}).Count -ge $jobs_for_move){sleep 10}
}

The move cmdlet has the switch ArchiveMailbox so it will try to move it, as its not there it cannot and thus gives you a warning.

Thanks for your Feedback. Sounds good. 
We will test the restores after migration (currently at around 20%), and when the source-repo is hidden from the VBO System - and when everything is fine, remove it after a while. 
 

Comment


Terms & Conditions