Warning: Site was moved to another url

[Helferlein]

Hi Veeam Forum members.

Since the update to VBO v4 my Sharepoint job always brings up the same warnings:

... finished with warning: Site was moved to another url.

Yes.. it's true that those sites were moved to another url. And we are aware of that.
Until when this message get repeated?
Is it possible to get this message remove after showing it like 5 times or so?

Thanks
Peter

[Polina]

Hi Peter,

We are aware of such issues and unfortunately cannot offer any solution or workaround for now. We're working on a hotfix and I'd suggest you open a support case to get it as soon as it's available.

Thanks!

[Helferlein]

Thanks Polina.

I will open a support case

[Funki_sahib]

Case # 03934889 answer from Support:

Fix in development status without any updates at the moment, it might take months to completer so I will update you as soon as it is released.

any Workaround possible to fix this problem?

[nielsengelen]

There is no workaround for now, a hotfix is in the process. We will update here as well once it is available.

[DaHe]

Any update on this, is there a date for this hotfix?

[nielsengelen]

Hi Daniel, if you update to 4a or 4b it should be resolved.

[DaHe]

I am on latest patch release 4.0.0.1553 of Veeam Backup for Microsoft Office 365 and still have the issue (status on update check: Your version is up to date!)

[nielsengelen]

Can you please contact support about this and let us know the support case ID?

[DaHe]

Case # 04000460 opened.

[DaHe]

Update on this:
Update to VBO 365 4b does not come automatically through internal update option, since this update is not working on the same host as Veeam B&R 9.5. So far I did not get a solution on top of Veeam B&R 9.5.

Veeam O365 4b worked on a VBO 365 standalone installation and should also work on top of Veeam B&R 10.

Important note:
Fix itself does not prevent "Site was moved to another url." warning. Therefore you have to add the url as an axclusion in VBO 365. With VBO 365 4b this exclusion is then handeled correctly.

[Polina]

Daniel,

The response is misleading - the hotfix is available for both VBO 4a and 4b. Your engineer will contact you shortly with the update.

Thanks!

[NoMercy]

Hi,

as a workaround for this problem you can remove the redirect site. Look here
at this Microsoft document:
https://docs.microsoft.com/de-de/sharep ... -redirects

1. Download and install Sharepoint Online administration shell
2. Open Powershell with elevated rights
3. Connect to your Sharepoint administration URL:

Connect-SPOService

4. Enter URL: https://contoso-admin.sharepoint.com
5. Enter Credentials of a tenant administrator
6. Enter URL of the redirect site, that has to be removed:

Remove-SPOSite -Identity https://contoso.sharepoint.com/sites/OldWebsite

7. Check removed URL in your browser. Browser should show „http 404“
(Perhaps you have to delete your browser cache)
8. Test your backup job in VBO to verify, that no warning appears

This worked for me.

kind regards
Arno

P.S.: Sorry for my poor english

[Mike Resseler]

@NoMercy

Never apologize for your poor english

Welcome to the forums, and thanks for this! I'm sure some of our other forum members will be able to use this and fix their problem! Really appreciated

[aarshe]

Hi,

as a workaround for this problem you can remove the redirect site. Look here
at this Microsoft document:
https://docs.microsoft.com/de-de/sharep ... -redirects

1. Download and install Sharepoint Online administration shell
2. Open Powershell with elevated rights
3. Connect to your Sharepoint administration URL:

Connect-SPOService

4. Enter URL: https://contoso-admin.sharepoint.com
5. Enter Credentials of a tenant administrator
6. Enter URL of the redirect site, that has to be removed:

Remove-SPOSite -Identity https://contoso.sharepoint.com/sites/OldWebsite

7. Check removed URL in your browser. Browser should show „http 404“
(Perhaps you have to delete your browser cache)
8. Test your backup job in VBO to verify, that no warning appears

This worked for me.

kind regards
Arno

P.S.: Sorry for my poor english

Thanks Arno! this worked perfectly! seems like a trivial change, i dont know why it's taking so long for the patch.

[agrob]

how about this warning message. Is Veeam implementing something that this warning is not showed more than 2-3 Times without the manuall remove as described from NoMercy in the future?

Thanks

[A.Rogers]

I used a workaround of excluding the old site address from the backup job using Veeam VBO powershell. Seemed to work well.

[Mike Resseler]

The problem of adding a warning message for this specifically and let it be gone after X amount of times is not a good practice imho. It could mean you are missing out on potential issues that are not foreseen. @agrob The manual remove has nothing to do with our product, but obviously removes the redirect site. Unless you want to keep that redirection for a longer period?

[agrob]

Thanks for your feedback Mike. I talked to our Sharepoint/Teams colleague and they don't want to remove the redirect.... So maybe you could implement an option for the customer to remove this particular warning message? so customer can decide by itself...

Thanks

[Mike Resseler]

Understood. It won't be in v6 as that is feature locked, but I assume that the redirect is needed for "lazy" users (And I don't blame them ) that have favorites. I will dive into a potential scenario on how to resolve it.

[agrob]

Thanks Mike. Well i think to keep the links "clean" would also be my preffered option but it seems not "to be possible".... So if there would be an option in the future, this would be nice

[agrob]

I used a workaround of excluding the old site address from the backup job using Veeam VBO powershell. Seemed to work well.

How did exactely did you add the old URL? I was able to add the url as exclusion, but when i check it in the veeam gui, the exlusion is shown as "site" and not as "team"

[agrob]

Sorry, i mixed things up.... the powershell command would be like this:

Connect-VBOServer -Server <SERVER>
#specifi Jobname and URL from Site you want to exlude from the Job
$jobname = "<BACKUP JOB NAME>"
$site = "<SITEURL_TO_EXLUDE>

$job = Get-VBOJob -Name $jobname
$organization = Get-VBOOrganization
$excludedsite = Get-VBOOrganizationSite -Organization $organization -URL $site
$excludeditems = New-VBOBackupItem -Site $excludedsite
Add-VBOExcludedBackupItem -Job $job -BackupItem $excludeditems

At the moment the job is running and i'll check if this workarround is working...

[A.Rogers]

Hi, Yeah I have the below saved which looks to match up with what you were retrying.

$job = Get-VBOJob -Name "VBO-SPO-01"
$organization = Get-VBOOrganization -Name "LLP.onmicrosoft.com"
$site = https://llp.sharepoint.com/teams/SharePointSite
$excludedsite = Get-VBOOrganizationSite -Organization $organization -URL $site
$excludeditems = New-VBOBackupItem -Site $excludedsite
Add-VBOExcludedBackupItem -Job $job -BackupItem $excludeditems

[A.Rogers]

There was 'teams' specifically in the site URL and not 'Sites' for the one I was looking at.

[agrob]

Thanks Alan

[RayS]

Hello, and thanks for this information. I'm running the above mentioned PowerShell to exclude redirect sites from my backup job. My attempts to do [Get-VBOOrganizationSite -Organization $organization -URL $Site] results in [Get-VBOOrganizationSite : The remote server returned an error: (401) Unauthorized] for all of the redirect sites in my tenant. I've confirmed it works for all other sites. It seems to be a permission issue, but I've not been able to determine what permissions are needed and for what account or Azure App. The organization is configured with Modern Authentication and Allow for using legacy protocols. With this, we're configured with an Azure App, using Application Secret to authenticate, as well as a service account with app password.

The Azure App has the following API permissions:
Microsoft Graph
Directory.Read.All
Group.Read.All
SharePointTenantSettings.ReadWrite.All
User.read
Office 365 Exchange Online
full_access_as_app
SharePoint
Sites.FullControl.All
Users.Read.All

The service account has Global Administrator and SharePoint Administrator roles assigned.



If SharePoint Site rename is now supported in v6, this can be ignored. But there was mention above that 6 is feature locked and it's not included. However the comment here post446796.html#p446796 suggests it is supported.

[RayS]

After upgrading to v6, the cmldet returns the [VBOOrganizationSite] object along with a warning as opposed to the error mentioned in my last post. This is now working for me.

[jorgedlcruz]

Thanks for the extra info, and for coming back with the update re v6.

[RayS]

In addition to the cmdlets working with V6 -- I am also very pleased to report that that I no longer have warnings for redirect sites.