Skip to main content

Backups Failing with Archive of the same name already exists

Thread needs solution
Beginner
Posts: 1
Comments: 0

Last night about 2/3rds of server backups failed with "Archive of the same name already exists". These are jobs that have been running for months and absolutely nothing has changed in the back infrastructure, backup jobs, on the servers or anything else. This feels like an Acronis Backup 12 bug as all the backups have failed at the same time. It has not been the first time I have had this error and the solution from Acronis support previously was to start a new backup with a new name, despite the fact that nothing changed. But this is the first time it has affected many servers all at the same time. I am annoyed that this is going to wreck my weekend, so I wanted to check if there are any fixes that don't include rebuilding all the backups from scratch. I do find Acronis errors do get treated as highly simplistic by support after we spend ages collecting a and sending logs and never receive a satisfactory answer as to why these issues occur.

0 Users found this helpful
Support specialist
Posts: 0
Comments: 550

Hello Tony,

welcome to Acronis forums!

Could you please share here a full activity log with this error message?

Beginner
Posts: 0
Comments: 1

I re-ran all the backups in the morning and they all succeeded without reporting the same error again. I made no changed to anything, just retried the backups. I have a suspcion that the issue lies with Acronis Cloud as the backups are all local, then replicate to the cloud. I had another problem with two backups since this error in which it said the cloud replication failed because it couldnt find some .XML file, I retried both backups, and again they worked.

Support specialist
Posts: 0
Comments: 550

Hello Tony,

thank you for sharing your steps in resolving this issue and the outcome.

Your suggestions and actions are correct: we recommend to Retry backup when  XML file that stores information about backup location gets corrupted.

Here is a KB article with possible causes and solution for issues with the error message "Failed to parse the XML"