Personal Site exclude but still error

[pierardy]

Hi,

Since 1 week, may be after we imported new users in AD/O365, I see this error type (many similar):

Failed to process site: https://company-my.sharepoint.com/perso ... company_be. Cannot contact site at the specified URL https://company-my.sharepoint.com/perso ... company_be. Access to this Web site has been blocked. Please contact the administrator to resolve this problem.

Backup job is:


and:


Why we have (now) errors on many Personal Exclude Site ? (460 errors "only" because we have +7000 users)

[nielsengelen]

Hi, per our forum rules, you should include a support case ID when posting technical issues. Can you open a support case and post the id here for future reference? Thanks.

[pierardy]

Hi,
I am now register my account on veeam but I do not know link to my existing licence.
Case : 04411353
I provide in this case my support ID.
May be you can ajust my new veeam account and attach to company profile.
Thanks

[pierardy]

Hi, per our forum rules, you should include a support case ID when posting technical issues. Can you open a support case and post the id here for future reference? Thanks.

Do you have any update for this case ?

[nielsengelen]

I see that the case is ongoing and logs are provided. For now, all we can do is let support do their part and hopefully find the solution/reason.

[pierardy]

Could you check my account registred because this case was created under VBO "demo" but we have support ID.
I want solve this issue quickly.

Thanks

[Polina]

Hi Yves,

First, no worries, our teams are fixing your account as we speak.
Next, your case is now on the radar of the VBO support team, so please stay in touch with the engineers to get it resolved. I can't be certain yet, but the issue you described looks very similar to a known problem; and if it's the case, support will provide you a hotfix very soon.

Thanks!

[pierardy]

Thanks Polina,
Yes, I receive hotfix and this is the solution.

I am waiting now for more specifics questions:
- Merge/Migration my Veeam account from old company to newone (before I was ProPartner with certificate VBR 9.5).
Actualy my new account is "standalone" account (no link with new company).
When new account is enrolled I want also merge my old account to newone
- Backup throughput is normal or too slow ? We have FO 1 Gb Internet
- 1 warning during backup about a url site (this url was changed in sharepoint)

[Polina]

Yves,

Have you got the account issues resolved now?

[dasfliege]

We had the same error message for several users of several customers. But in our case, we didn't excluded those users. They didn't even appear in the user list. All of them were deleted users whos retention period (30 days deletion and 93 days recycle bin) has already expired, but O365 didn't deleted them properly. Their personal site still existed somehow. I was able to fix that issue via a few powershell commands. I can supply them, if someone has the same problems. Just let me know.

[Mike Resseler]

@dasfliege
Feel free to share them, I am sure you will help our community with this!

Thanks
Mike

[dasfliege]

There you go:

These steps must only be performed, if the user throwing the warning message isn't visible anywhere in the MS Online Admin Portals.
In our case, we had a few "orphaned" personal sites from users which have been deleted more then a year ago. The default retention for user deletions are 30 days + 93 days. During the 30 days retention, access to the deleted users data is automateically beeing granted to the manager of the deleted user. During the 93 days retention, the user isn't visible anymore in the admin center, but it's still possible to restore the account via powershell.
Before you perform below steps, make sure that the retention for the deletion is already over. If the personal site isn't listed by firing "Get-SPODeletedSite", then you can proceed with the following steps:

1. Open an administrative Powershell
2. Download SPO Module if not already present: "Install-Module -Name Microsoft.Online.SharePoint.PowerShell"
3. Connect to your Tenant and login as global admin: "Connect-SPOService -Url "https://examplecompany-admin.sharepoint.com"
4. Check if the user still exists somewhere in your organisation: "Get-SPOUser -site "https://examplecompany-my.sharepoint.com"
5. If the user still exists here, delete it: "Remove-SPOUser -Site "https://examplecompany-my.sharepoint.com" -LoginName <email adresse of the user>
6. Check if the personal site of the user still exists. The exact URL of the personal site is included in the warning message that Veeam throws: "Get-SPOSite "https://examplecompany-my.sharepoint.co ... ompany_com" | select *
7. If step 6 returns a record, check if "LockState" is set to "Unlock". If not: "Set-SPOSite "https://examplecompany-my.sharepoint.co ... ompany_com" -LockState Unlock
8. Delete the orphaned site: "Remove-SPOSite "https://examplecompany-my.sharepoint.co ... ompany_com"

[paulpreichE4]

Hi

We are running Veeam Backup for Office365 5.0.3.1033.

Veeam Case: 05011452

Over a month ago we had an O365 administrator disable and de-license a user account. The OneDrive backup job we have running began to fail for the user's personal site with: 'Failed to Process Site: https://customer.sharepoint.com/personal/user'. Cannot contact site at the specified URL. Access to this website has been blocked. Please contact the administrator to resolve this problem.

When we went to exclude the site, no personal site was found for the user in the GUI. If we attempt to exclude via Veeam Office 365 PowerShell cmdlets, we run into an 'Access Denied'.

The O365 administrator has confirmed that this personal OneDrive no longer exists. It is not in the site collection recycle bin. Furthermore, using the Sharepoint Online Powershell cmdlets, the O365 administrator initiated a query for the personal site URL and no site was found. "

Veeam support is suggesting that this is a Microsoft issue, but my client and I disagree. Has anyone ever ran into an issue like this?

[HannesK]

Hello,
and welcome to the forums.

As I understood there is a 403 HTTP error instead of 404, I tend to agree with our support. Did you already try the solution from above?

Thanks,
Hannes

[Polina]

Hi Paul,

How is your job configured? Is it a backup of an entire organization, or explicitly selected users/sites?