Symptoms
When a user attempts to perform a backup of Microsoft Teams, the backup succeeds with the following error message:
"Could not get Channel Messages: Error: 403 GET"
C2C backups
Symptoms
- The Tenant is located on EU1 DC or EU8 DC
- You have noticed that C2C backups have been pending for 100+ hours.
Cause
Issue is caused by lack of DC resources to process the current number of C2C tasks.
This issue is fully resolved.
Symptoms
After C23.02, C2C Backups are stuck in Pending state and don't progress:
Cause
Issue in the product.
The issue is solved in a new scheduler version implemented in the last update C23.02 but it's being enabled on datacenters gradually. Until that, the C2C backups will process with a delay. In the meantime, please use the workaround mentioned above.
Symptoms
- You are using the storage abgw-sin2-acs1.acronis.com on SG1 DC
- Since the beginning of March, backups have been failing with “[Archive Server]: Storage request timeout” or "The cloud storage is temporarily unavailable"
Cause
Issue is caused by lack of hardware.
This issue is resolved.
Symptoms
- You have a protection plan for Microsoft Teams
- Recently, backups started reporting the warning: "Failed to load tabs in channel 'General': 'Error: 400 GET’"
Cause
Issue in the product. The issue is caused by unexpected changes in Microsoft API.
Acronis Development team is working on a fix.
Symptoms
- You are creating a new C2C backup plan or editing an existing one in the Management tab
- When choosing the items to back up, you are unable to select the groups "All" ("All users", "All Teams", etc.).
The checkbox is grayed out:
Cause
Issue in the product.
This issue has been resolved.
Symptoms
- You are using the storage abgw-lhr3-arp1.acronis.com on EU1 DC
- Starting from 28th of April, C2C backups and physical backups are failing with errors “Storage request timeout” or “Operation failed due to a temporary issue in the cloud storage”
Cause
Issue in the product.
This issue has been resolved.
Symptoms
- You back up Microsoft 365 or Google Workspace resources using C2C (Cloud-to-Cloud) backup method
- In the Cyber Protection Console, the "Next backup" date remains in past or shown as "Not scheduled", although backups run every day
Symptoms
- You're trying to backup or recover C2C backups (Cloud-to-Cloud backups of Microsoft 365 and Google Workspace)
- The activities fails with "Task timeout expired. The agent that is responsible for processing the task is not accessible."
Symptoms
When attempting to perform a Cloud-to-Cloud backup, the backup operation fails with the following message:
[Archive Server]: archive session not found
Cause
This is a known issue in the product.
Solution
The Acronis Team is currently working on a fix. This article will be updated as soon as the issue is resolved.
Symptoms
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"
Cause
The backup index was not properly updated.
Solution
The following solution can be applied by a partner administrator:
Symptoms
- You are using US5, EU2 or EU8 DCs
- Starting from end of April, C2C backups haven't been running automatically
- Attempt to start backup manually works fine.
Cause
Issue on DC side.
Acronis Development team is working on a fix.
In the meantime, please follow the workaround below:
Symptoms
- Starting from 25th of February, backups to Acronis Cloud fail with error: “get meta with key \".backupScheme\": [Archive Server]: archive is corrupted”
- This issue mostly affects EU1 and SG1 DCs. Affected storages are abgw-lhr3-arp1-r01.acronis.com, abgw-sin2-acs1.acronis.com
Cause
C2C archives corruption due to the storage incidents.
Symptoms
- Since January, C2C backups of Microsoft 365 have been failing with "Internal error"
Cause
Issue in the product.
Solution
The issue is fixed in the beginning of May.