[SOLVED] ATIH fails to backup "Failed to renew certificate"
ATIH 2016 b6027
Dear Acronis team I have setup a new OS and according Acronis backup job and for the first time I am using the Cloud Service instead of a local / external disk.
I also enabled encryption for the backups and email notifications.
Now I noticed that the backup fails with the given message on the screenshot.
What can I do now?
Attachment | Size |
---|---|
acronis_certificate.png | 316.49 KB |


- Log in to post comments

Hi Karl,
See if one of these helps - looks like you may be able to manually clear the old cached certificate and the Cloud should then sync backup and recreate it:
https://kb.acronis.com/content/56025
Solution
There might be several root causes of the issue:
- Your Cloud subscription has expired. To continue using Cloud backup you need to renew subscription.
- You have renewed your Cloud subscription, but certificate was not updated. Current versions of Acronis products automatically obtain the renewed certificate upon getting this error, so make sure you are using the latest available build. On older versions (and on Acronis Backup for VMware) renewal can be manually triggered via removal of the cached certificate. Renew the certificate as described in this article.
- Subscription is not tied to the Agent doing backup. For example, you were backing up virtual machines using Virtual Appliance, then you started backing up with Agents installed into the guest OSs. Find the agent tied to the subscription: log in to your account on Acronis website, navigate to Cloud Backup for Business and click Recover files from Acronis Cloud. Here you can view list of machines backed up by the subscription and respective archives. Reassign subscription as described here.
- Subscription conflict when using multiple Virtual Appliances, e.g. Machine1 was backed up by VA1, Machine2 was backed up by VA2. Backup will fail if VA2 starts to back up Machine1, because backups of Machine1 are managed by subscription of VA1. We recommend to use binding of virtual machines to prevent backup failures.
- Archive naming conflict when backing up multiple machines to one account. For example, you have started a backup of Machine1 to Archive1, but the backup failed (and therefore is not displayed in the vault), then you start backing up Machine2 and give its archive name "Archive1". Backup fails since this archive name is already in use, although this archive does not contain any completed backups and is not displayed. In this case you need to rename the archive of Machine2.
This one is a little more vague, but also mentions this occurring for someone else...
https://forum.acronis.com/forum/99612
- Log in to post comments

Thanks for your kind help guys. I haven't found the time to elaborate your solutions soon enough, but sometimes TIME DOES HEAL IT world problems.
Just wanted to say that the issue is gone without any interaction on my end and the cloud backup does work normally now according to the application.
- Log in to post comments