Exclusion missing error

[b.vanhaastrecht]

Hello,

What's the reason for this message to be a Error and not informational?

Code: Select all

12-10-2022 23:39:12 :: Some excluded objects were not resolved. Failed to resolve user (name: <username>, ID: dc0c4c78-794c-4f38-981e-2c2eb5exxxxxx:00000000-0000-0000-0000-000000000000) :: 0:03:01

It's excluded, so not important, why make it important when the excluded object is even removed.

Kind regards,
Bastiaan

[Mildur]

Hi Bastiaan

I run a test in my lab.
1) Excluded user from a mailbox job
2) Run the backup job
3) permanently deleted the user in M365
4) run the job again

I didn't get this error message in my lab.
Was the user deleted a long time ago? Or in the last few days?

Best
Fabian

[b.vanhaastrecht]

Hi Fabian

In the audit logs of Azure AD we find log entry for this user: "Hard Delete user"

This means it has passes the 30 days soft delete. So after a user is permanently deleted, we get this errors.

And, if we remove this exclude of the hard deleted user in VBO, run the job again, we get the same error now for a next Hard deleted user. So the job seems to error out on the first not-found excluded user, and then seems to stop processing the next not-found excludes.

[Mildur]

Hi Bastiian

I also see my test user as hard deleted. I also tried it again with a OneDrive Job. I don't get the error message for permanently deleted users which are excluded in the job.
Which VB365 version are you running? I don't see this error in the latest one: 6.1.0.423 P20220926.

Maybe it's worth to open a case with our support team and let them check the log files. Please provide me with the case number. I will follow the case from our side (PM).

Thanks
Fabian

[b.vanhaastrecht]

I'm running v6a P20220825 which is the latest public available version.

I will create a support case.

[Mildur]

The latest public version is 6.1.0.423 P20220926
https://www.veeam.com/kb4106

We released a cumulative update last week.

[b.vanhaastrecht]

Ok, not according this this page: veeam-backup-for-microsoft-365-f47/curr ... 39185.html

I will update to the latest version, could you please update that forum page.

[Mildur]

Yes, I know.
That topic will be updated soon.

[b.vanhaastrecht]

Ticket created: 05672232

[b.vanhaastrecht]

The update to P20220926 did not change the behavior and we still have the issue. Support is investigating it.

[Mildur]

Thanks for the update.

[b.vanhaastrecht]

This tenant was configured to use modern auth with legacy support. We reconfigured the authentication to modern only, and now there are no more errors like this.

Just to be sure we also run a repair on "C:\programdata\veeam\backup365\configDB\config.edb", this gives an error and this is still being investigated.

[Polina]

Hi Bastiaan,

Thank you for the update. Honestly, I'd expect to see the same behavior regardless of the authentication method used. I'll discuss it with our engineers to get more details.

[b.vanhaastrecht]

Hi Polina,

Yes, my toughts were exeactly the same but the engineer told me that the backup method with modern authentication is different from basic authentication.

I just spoke with the support engineer and the database problem is something else. So my issue is resolved by switch to modern authentication only, no legacy.

[Polina]

We're at the point when legacy goes away anyway, as Microsoft has already started to switch off basic protocols. Nevertheless, I'll talk to the team to understand what affects the behavior.

Thanks!