Hi,
how does Veeam Backup for Microsoft 365 handle soft deleted objects, for example, a deleted group that is retained for 30 days?
Our customers often report warnings that dependent resources of a group cannot be backed up because the group has been deleted, e.g. the group mailbox:
Processing mailbox Test failed with error: Failed to process team: Test. Team mailbox not found: Test (ID: XYZ)
Processing mailbox Test completed with warning: Group mailbox not found
Our customers then receive a warning in the backup job, even though the group was deleted correctly and the backup job backs up the entire organization as desired.
What is the best practice here or is there already a feature request that soft deleted objects can be excluded from the job?
BR
Lukas
-
- Service Provider
- Posts: 34
- Liked: 5 times
- Joined: Jan 17, 2023 7:17 am
- Full Name: Lukas Krusberski
- Contact:
-
- Veeam Software
- Posts: 3718
- Liked: 903 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Handling of soft deleted objects
Hi Lukas,
Soft deleted objects are out of the backup scope - we cannot access them.
I can only provide you an educated guess on the potential root cause. When backing up a team, the corresponding group also has to be protected because of their dependencies. In some cases, a group might be deleted, while the team is still there, and in such a case we try to back up the team and then its corresponding group and fail to access it. This could be the case why you see such error messages.
To confirm the root cause and resolve the issue, it'd be best to open a support ticket and let our engineers investigate logs.
Thanks!
Soft deleted objects are out of the backup scope - we cannot access them.
I can only provide you an educated guess on the potential root cause. When backing up a team, the corresponding group also has to be protected because of their dependencies. In some cases, a group might be deleted, while the team is still there, and in such a case we try to back up the team and then its corresponding group and fail to access it. This could be the case why you see such error messages.
To confirm the root cause and resolve the issue, it'd be best to open a support ticket and let our engineers investigate logs.
Thanks!
-
- Service Provider
- Posts: 34
- Liked: 5 times
- Joined: Jan 17, 2023 7:17 am
- Full Name: Lukas Krusberski
- Contact:
Re: Handling of soft deleted objects
Hi Paulina,
thank you for your reply. I can only agree with your assumption, and I have already sent our customer Microsoft instructions so that the groups can be deleted immediately using “hard delete.”
Our customer only asked us to contact you and inquire whether VB365 could be checked to see if the objects had been deleted.
He would like to prevent the warning, as he sees no reason for it.
Probably in the direction of a feature request.
BR
Lukas
thank you for your reply. I can only agree with your assumption, and I have already sent our customer Microsoft instructions so that the groups can be deleted immediately using “hard delete.”
Our customer only asked us to contact you and inquire whether VB365 could be checked to see if the objects had been deleted.
He would like to prevent the warning, as he sees no reason for it.
Probably in the direction of a feature request.
BR
Lukas
-
- Veeam Software
- Posts: 3718
- Liked: 903 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Handling of soft deleted objects
Hi Lukas,
Unfortunately we cannot identify it immediately within the product, and neither there's a way to suspend such warnings. But I'm taking it as a FR.
Thanks!
Unfortunately we cannot identify it immediately within the product, and neither there's a way to suspend such warnings. But I'm taking it as a FR.
Thanks!
Who is online
Users browsing this forum: No registered users and 11 guests