Backup Manager API deprecation - is there going to be a replacement?

[Jakub Gladykowski]

Hi!

I got email about Backup Manager API deprecation of those API endpoints:

Export APIs
• /rest/backup/1/export/runbackup
• /rest/backup/1/export/lastTaskId
• /rest/backup/1/export/getProgress

We use those to backup our instance on a regular basis. Will there be another point to do it? Are there plans to backup without manual intervention?

[jsinger_ips · Accepted solution]

Got this email too, this morning. 

I just did a support chat with the Atlassian support AI and it said the following:

---

I understand your frustration regarding the recent communication about the Backup Manager API deprecation.
Atlassian is officially closing the Backup and Restore CLI Early Access Program on March 31, 2025. After this date, the CLI tools will no longer be available, and you’ll be transitioned to a new backup and restore solution.
This new solution offers a self-serve user interface, public APIs, support for more products, and improved scalability and reliability.
However, there are some changes in backup and restore limits, automation options, and access permissions that may impact your workflows

---

I asked "Your email says we will have to create backups manually. Do you seriously think that is acceptable ?"

---

You’re right to be concerned—having to create backups manually is not ideal for many organizations.
However, with the new backup and restore solution being rolled out, you do have the option to schedule backups to run automatically, including daily backups if needed.
You can also choose to store these backups in Atlassian storage (retained for 14 days) or your own Amazon S3 storage (retained for 30 days).
Automation is supported via public APIs, so you’re not limited to only manual backups

---

I asked 'Will the new backup system be available on JIRA cloud standard ?'

---

The new backup and restore system is currently being rolled out for customers on the Enterprise plan through a beta program.
At this time, it is not generally available for Jira Software (Cloud Standard) plans.
The documentation specifies that this enhanced backup and restore experience—including features like scheduled backups and Amazon S3 storage—is limited to the Enterprise plan during the rollout

---

[Sunny Ape]

Hello @jsinger_ips 

Well, that explains everything. It was just final closure email being sent out regarding the 2024 EAP and the closure of the APIs that were part of that experimental program.

Looks like the AI bot has provided detailed information about what is currently being offered as an alternative and which customers are going to get that offering and how.

Sounds like a match for what was described in the correspondence for the participants of that EAP.

I guess that infers trying the new Atlassian Cloud Backup Management REST APIs.

[Mads Kristiansen]

But the new backup API endpoitns are still not good enough for many customers. 30 day retntion is nothing in many organizations, along with not being able to take offline backup, and not to talk about archiving backups for compliance needs. 

I really hope for Atlassian that they will have some major retooling of their new internal backup solution.

It does look like the new backup tooling is very limited to ensure that they do not eat marktplace apps dinner. 

I must say, this is scarry.

[Sunny Ape]

Hello @Jakub Gladykowski 

I'm not aware of any announcements from Atlassian about the deprecation of any official 'Backup Manager APIs' for Jira Cloud, so it's not clear who or what sent that email to you.

Also, those API URLs you have provided are not part of the public Jira Cloud REST APIs, they appear to be some of Atlassian's private, internal, undocumented APIs that are subject to change without notice.

[Jakub Gladykowski]

Atlassian sent this email. Who else could have done it ? 

Fact that those APIs are internal and undocumented is irrelevant. They were only way to do backups in an automatic way, so from functional point of view this was official way to do it.  

[Sunny Ape]

My apologies @Jakub Gladykowski  , I wasn't a participant in that particular EAP, so had no idea about those trial API endpoints that were available for the duration of the program. I assume that the email you received was only sent out to those Org Admins or the designated support contacts for the organisations who participated in that program.

Atlassian are normally very communicative to all EAP participants. I would have thought that, when the program ended in March this year, they sent out extensive information advising all the participants of the outcome of the program, including the deprecating of those v1 APIs as well as notification of the new, public v2 APIs that were introduced to replace them.