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.
EU1 DC
Symptoms
- Your tenant is located on EU1 DC and uses storage baas-fes-eu7
- Since last week, backups to Cloud have been failing with "The newer version of the object already exists"
- In the error text, you see that Agent refers to another storage: "fesAddress: abgw-lhr3-arp1-r01.acronis.com:44445"
Symptoms
- You are using the storage abgw-lhr3-arp1.acronis.com on EU1 DC
- Starting from 24th of March, backups have been failing with “Operation failed due to a temporary issue in the cloud storage”
- In the error details, you see the messages “Object is invalid” and the archive name in the “path” field:
Symptoms
- In the end of December, 2022 an issue occurred where C2C backups are pending in the "Queued" status on EU1 DC or miss the scheduled start.
- Attempt to run backup manually finishes with the error "Workload is already being backed up"
Cause
Performance issues on EU1 DC.
This issue has been resolved.
Symptoms
- The Tenant is located on EU1 DC
- C2C backups are failing with “Cannot open or create backup file. [Archive Server]: internal error” starting with October 2022
Cause
The issue is caused by an incorrect DNS configuration on DC.
Solution
This issue has been resolved.
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.