Backing Up "Office 365" Group Types

[ctaylor]

When trying to backup "Office 365" Group Type mailboxes, we are receiving failures with the following warning "Failed to find group owner account."

Permissions have been set for the Veeam backup account according to the guide here: https://helpcenter.veeam.com/archive/vb ... sions.html

All other mailboxes are being backed up properly, this is only happening on these newly added "Office 365" Group Types - as opposed to Distribution Lists or Mail-enabled security groups.

[Mike Resseler]

Hi Chris,

First: Welcome to our forums!

Second: Can you check in the administrator view of O365 (not VBO) if those groups have an owner? https://support.office.com/en-us/articl ... d540e45732
The link is not completely what you need but gives you a view how to look at group ownership

Let me know
Mike

[sgun]

V. 2 seems to be attempting to backup Yammer groups at least in my environment, this warning is generated on groups originated with Yammer.

When attempting to backup closed Yammer groups, an error is generated:

31-07-2018 03:00:27 :: Processing mailbox alleosderelskergif@xxxxx.onmicrosoft.com failed with error: Failed to access mailbox.. Access is denied. Check credentials and try again., User '/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=fd3a192ad80e4cd882e714bd0e515201-yyyyyy' not authorized to access group 'alleosderelskergif@xxxxx.onmicrosoft.com'. Reason: '(0xD10)'. :: 0:00:53

Not sure why VBO tries with a seemingly random account. Specific account is not a member of group, and different random accounts are used on different groups.

Would be nice to be able to exclude Yammer from email backup.

[Mike Resseler]

Soren,
Are you using Yammer Groups that are associated with Office 365 groups?

[sgun]

Yammer is integrated with our Office 365 to the best of Microsoft's ability, so the answer would be yes.

We enforce Office 365-id in Yammer and Yammer groups are by consequence automically activated in Office 365, or so I believe.

[Mike Resseler]

Soren,

In that case, please create a support call. If it is integrated, there should not be a problem to the best of my knowledge. Please post the case ID and outcome (after the investigation) here

Thanks
Mike

[clintg]

Did anyone ever find the solution to the original question? I am getting the "failed to find group owner account" warning on groups that were created only in office 365. They do have owners and I checked all the permissions according to the documentation.

[Mike Resseler]

Hi Clint,
The OP has not given a support call ID so I cannot check. If the group owners are created, then please create a support call and post the case ID here (and the outcome afterwards)

Thanks
Mike

[wpflores]

Hi Mike, I have the same issue. My ticket 03130695 was opened to address several warning in the backup job using the new Veeam Office365 backup. Two of the warnings were this exact issue - Group type was Office365. Both groups were created online, had 1 member in the group, and that member was also the owner. The tech on my case suggested I post this issue in the forums.

We ended up deleting the 2 groups since they were test groups anyway. Of course that cleared the warnings because we were working toward a more difficult issue. But the question remains, what caused the warnings of why Veeam couldn't backup these types of groups?
Thanks,
Wes.

[Mike Resseler]

Any change these were yammer groups?

[sgun]

As per Support Case 03129154, there is a known bug in VBO 2.0 where it fails to resolve group owners if alias to group owner has a space in it's name.

"Veeam tried to use seemingly random accounts for backup of group mailboxes because it was not possible to resolve the group owner account for it.
This is caused by the fact that the group owner account has spacings in the UPN alias.
This situation is, unfortunately, caused by one of our known issues. Our R&D team is currently developing a fix for it."

A fix has now been released for this and it has resoived at least our problem. Workaround: exclude O365 groups from backup, and then exclude group members from this exclusion.

[Mike Resseler]

Soren,

You talk about the workaround, but also about a fix. What exactly applied to you? I'm not sure

[sgun]

Hi Mike,

Both actually. First the workaround by excluding all existing o365 groups, then the fix which addresses the issue on newly created groups (so I don't have to keep excluding new groups and remembering to include their members).

[Mike Resseler]

Good. So a fix has been given to you to solve it permanently.

Thanks for letting us know

[wpflores]

Mike, sorry for the delayed response. In my case these were not Yammer groups.
Soren, I'm curious what fix was provided to you? I haven't heard of any fix so far.

Thanks,
Wes.

[sgun]

Fix_140096_2a242e3098.zip containing Veeam.Archiver.Source.dll which needs to be copied to two diffent locations.

[lowlander]

Hi,

is the fix already included in version 2.0.0.567, or does it has to be installed on top of it ?

thanks !

[Mike Resseler]

Hi Lowlander,

No. The version should be .594. The hotfix rollup package is here: https://www.veeam.com/kb2765

[westinbuilding]

This bug regressed in v3.0.0.422.

https://imgur.com/a/tNpuK6M

[nielsengelen]

Hi Nick, please contact support for insight and a solution.

[Mike Resseler]

Nick, please let us know the support ticket and the outcome. I would like to take this support ticket number to our DEV team
Thanks
Mike

[westinbuilding]

Case #03512072

Now I am getting runarounds...According to Veeam Support, I need to make sure that the group has an owner account.

According to Office365 Support, members that have Full Access to the Share Mailbox is equivalent to being the Owner.

Both sides' conditions are satisfied, and yet, I can't have a good backup....

[Mike Resseler]

Nick,

So the specific group does have an owner? (You can use this article to verify: https://support.office.com/en-us/articl ... d540e45732). Or is this a shared mailbox?

[westinbuilding]

this is a shared mailbox.

[westinbuilding]

Veeam Support - Case # 03512072

[Mike Resseler]

Hey Nick,

I just looked through your case, and you are going to arrange this together with MFST and Veeam in a joint conference call in a few days. I would appreciate it if you could give us the outcome of that
Thanks
Mike

[westinbuilding]

gotten the runaround and finger pointing between the two support team, for some reason, they all think I am talking about 'groups', as you put users in the member of, not shared mailbox...

We've since abandoned the shared mailbox idea (because can't backup) and moved away from Veeam for this customer...

[Mike Resseler]

This is strange. I have shared mailboxes in my test environment and they are protected. I realize that you don't use Veeam for the customer, but can I ask you for one last question?

What where the settings for that shared mailbox?
* Does it have an email alias?
* Is email forwarding configured?
* Sent items configuration?
* Email apps allowed?

At least if you can still access that information
Thanks
Mike