Summary

There have been a few changes on the endpoints around the backup manager which caused the script we provide customers with to fail. See How to Automate Backups for JIRA Cloud applications.
One of the changes was that the endpoint to trigger the backup has changed from rest/obm/1.0/runbackup to rest/backup/1/export/runbackup.

The other one, which I have not been able to workaround it, is that the endpoint to get the progress on the backup creation, rest/backup/1/export/getprogress.json is now returning a 404.

Through the browser's development panel, it's been identified that the endpoint rest/internal/2/task/progress/<task_number> is now called to retrieve the backup progress.

Symptoms

1. End to trigger the backup, /rest/obm/1.0/runbackup, now returns "Oops, you've found a dead link.".
2. Progress check endpoint, /1/export/getprogress.json, not returns a 404.

Steps to Reproduce

1. Trigger a backup
2. Run

   curl -D- -u <user>:<pass> -X GET https://<instance>.atlassian.net/rest/backup/1/export/getprogress.json

Expected Results

The backup progress is returned successfully.

Actual Results

A 404 HTTP is returned instead.

Workaround:

The taskId is returned after triggering the backup through the endpoint rest/backup/1/export/runbackup. The returned JSON looks like this:

{"taskId":"10109"}

Customers will need to adjust their scripts to capture the taskId accordingly.