Cloud storage is overused by backups of M365 (Teams, One Drive, etc) or Google Workspace (Google Drive).
Backup storage size is several times bigger than the backed up data.
There are multiple causes why the C2C backups consume significantly more storage space than the data being backed up. Data handling works differently because of some peculiarities of the source storage itself.
1) Data deleted from the source is still included in the backup
Backup, recovery, or other operations with Microsoft 365 items fail with the following error:
.NET exception 'System.Net.WebException' has occurred: The underlying connection was closed: An unexpected error occurred on a send
This applies both to C2C backup and to local Agent for Microsoft 365.
Microsoft 365 Cloud-to-Cloud (C2C) backup or restore jobs are being executed slower than expected and take significant time to complete.
Cloud-to-Cloud backups are not that dependent on the total size of the backed up data (though this also has its role) but rather on the number of items that are being backed up.
Each separate item creates a separate request to Microsoft and depending on the number, throttling can be enabled on Microsoft side to reduce the load.
When performing a Cloud-to-Cloud backup of a Microsoft 365 Public Mailbox Folder, the backup operation fails with the following error message:
XML syntax error on line 1: invalid characters between </ and >: error while reading SOAP response
Performance issues on EU1 DC.
This issue has been resolved.
The issue is caused by an incorrect DNS configuration on DC.
This issue has been resolved.
When attempting to perform a Cloud-to-Cloud backup, the backup operation fails with the following message:
[Archive Server]: archive session not found
This is a known issue in the product.
The Acronis Team is currently working on a fix. This article will be updated as soon as the issue is resolved.
While browsing existing Cloud-to-Cloud backup archives, the user is unable to access the backup archive and receives the following error message:
"The search is not available because this backup is not cataloged yet"
The backup index was not properly updated.
The following solution can be applied by a partner administrator:
Attempting a Microsoft 365 Cloud-to-Cloud (C2C) backup job fails with the following error:
A configuration error: 'Could not access to Drive 'b!XHg8hoZeCkKvMNIhzQxlEDATIZDBKWROls50ZZtT0BdVgIJASW43SKq-Xdj34Aqo': ms graph error httpStatus: 429, code: activityLimitReached, message: The request has been throttled'
Backup of Microsoft 365 resources fails with the following error:
The following quota is reached: Number of protected Microsoft 365 seats
Changes in the Microsoft 365 licensing in Per Workload model in C21.10: Microsoft 365 resources require Seat quotas.
The Microsoft 365 seats that are subject to a per-seat license are:
