TERRA CLOUD Veeam Data Protection Fehlerdiagnose/en: Unterschied zwischen den Versionen

Aus TERRA CLOUD WIKI
FuzzyBot (Diskussion | Beiträge)
Übernehme Bearbeitung einer neuen Version der Quellseite
Die Seite wurde neu angelegt: „== Processing mailbox <Name> completed with warning: Cannot protect a group mailbox because the group doesn't have an owner ==“
 
Zeile 23: Zeile 23:
# Enter the desired user in the "Exchange Online Web Services configuration" section and confirm the change using "Apply."
# Enter the desired user in the "Exchange Online Web Services configuration" section and confirm the change using "Apply."
[[Datei:Change-Impersonation-User.png|1200px]]
[[Datei:Change-Impersonation-User.png|1200px]]
<div lang="de" dir="ltr" class="mw-content-ltr">
== Processing mailbox <Name> completed with warning: Cannot protect a group mailbox because the group doesn't have an owner ==
== Processing mailbox <Name> completed with warning: Cannot protect a group mailbox because the group doesn't have an owner ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<div class="mw-translate-fuzzy">
'''Fehlerbild:'''<br>
'''Error:'''<br>
Sie erhalten die folgende Warnmeldung für Ihren Microsoft 365 Backup Job: <br>  
You receive the following warning message for your Microsoft 365 backup job: <br>
[[Datei:No owner.png|ohne|600px]]
[[Datei:No owner.png|ohne|600px]]
'''Ursache:'''<br>
'''Cause:'''<br>
Die Sicherung von Microsoft Gruppenpostfächern über das Veeam Backup für Microsoft 365 ist nur möglich wenn dieser Gruppe ein Eigentümer zugewiesen ist. Ohne diese Zuweisung ist ein [https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/impersonation-and-ews-in-exchange Identitätswechsel] nicht möglich. <br>
Backing up Microsoft group mailboxes via Veeam Backup for Microsoft 365 is only possible if an owner is assigned to this group. Without this assignment, [https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/impersonation-and-ews-in-exchange] impersonation is not possible. <br>
Es handelt sich um ein bereits bekanntes Microsoft und Veeam Problem. <br>
This is a known issue with Microsoft and Veeam. <br>
'''Lösung:'''<br>
'''Solution:'''<br>
Bitte weisen Sie den aufgeführten Gruppen aus der Warnmeldung einen Eigentümer zu. Eine Anleitung dazu finden Sie in diesem [https://support.microsoft.com/en-us/topic/assign-a-new-owner-to-an-orphaned-group-86bb3db6-8857-45d1-95c8-f6d540e45732 Microsoft Artikel].
Please assign an owner to the groups listed in the warning message. Instructions can be found in this https://support.microsoft.com/en-us/topic/assign-a-new-owner-to-an-orphaned-group-86bb3db6-8857-45d1-95c8-f6d540e45732 Microsoft Artikel].
</div>
</div>
<span id="Wiederherstellung"></span>
<span id="Wiederherstellung"></span>

Aktuelle Version vom 24. Juni 2025, 09:50 Uhr

Backup

Failed to access public folders.. There are no public folder server available.

Error pattern:
You receive the following error message for your Microsoft 365 backup job:

Cause:
The user stored in the Entra ID application for Microsoft 365 data backup cannot be used for impersonation in Exchange Online Web Services.
Therefore, a backup of public folders is not possible. For impersonation, the user requires an Exchange Online license and the required permissions.
Solution:
Please check the configured user in the Entra ID application in the Veeam Backup for Microsoft 365 plug-in in the Protection Portal.
When linking the organization, the user specified during setup is initially stored here.
You can either change the stored user using the following instructions or grant the existing user a license and, if necessary, authorize them in the Microsoft 365 Admin Center.
Configuring the user for impersonation:

  1. In the Protection Portal, click the gear in the upper right corner to access the configuration.
  2. Select the Veeam Backup for Microsoft 365 plug-in.
  3. In the "Organizations" section, edit the desired tenant using "Edit."
  4. Click the ID in the "Application settings" section.
  5. Enter the desired user in the "Exchange Online Web Services configuration" section and confirm the change using "Apply."

Processing mailbox <Name> completed with warning: Cannot protect a group mailbox because the group doesn't have an owner

Error:
You receive the following warning message for your Microsoft 365 backup job:

Cause:
Backing up Microsoft group mailboxes via Veeam Backup for Microsoft 365 is only possible if an owner is assigned to this group. Without this assignment, [1] impersonation is not possible.
This is a known issue with Microsoft and Veeam.
Solution:
Please assign an owner to the groups listed in the warning message. Instructions can be found in this https://support.microsoft.com/en-us/topic/assign-a-new-owner-to-an-orphaned-group-86bb3db6-8857-45d1-95c8-f6d540e45732 Microsoft Artikel].

Recovery

Problems adding the Restore Portal Application in Entra ID

Error:
When running the application Connect-VB365RestorePortal, you receive an error message when adding the Restore Portal Application or assigning permissions for it.
The Entra ID Enterprise Application of the TERRA CLOUD Veeam Data Protection Restore Portal must be added and authorized once for a restore.
Instructions for manually adding the Restore Portal Application
1. Start PowerShell as an administrator
2. Install the Microsoft Graph module

Install-Module Microsoft.Graph

3. Run the "Connect-AzureAD" cmdlet to launch a login dialog for Entra ID

Connect-AzureAD

4. Please log in to a user with the "Global Administrator" role in the Microsoft 365 tenant for whom the application is to be added.
5. Add the Entra ID Enterprise Application using the "New-AzureADServicePrincipal" cmdlet

New-AzureADServicePrincipal -AppID "c3a749b0-ec1f-4b2b-af40-316172f7d71a"

6. Open the Microsoft Entra ID Admin Center and search for a corporate application named "TERRA CLOUD Veeam Data Protection - Restore Portal" (remove the filter if necessary).
7. Grant administrator permission for the desired tenant in the "Security --> Permissions" section (see screenshot below).
8. Check whether you can now log in to the Restore Portal.