For the past couple of years, we have had a python script built to prepare a backup of all of our Confluence Cloud spaces, and upload the backup to an AWS S3 bucket. For the past couple of months, this script has been failing sporadically, despite no changes being made to the underlying code.
The backup is kicked off by issuing a post request to the following URL:
"<accounturl>.atlassian.net/wiki/rest/obm/1.0/runbackup".
We would then get the progress with a get request to the following URL: "<accounturl>.atlassian.net/wiki/rest/obm/1.0/getprogress".
The second request would continue to execute in a loop until the status of the response indicated success, which then a file name and location would be generated that we could download.
During failed runnings of this script, the script gets stuck in its loop while getting the progress, as the process never succeeds. The backup is never prepared on Confluence's end, which would then be downloaded and stored for the long term.
When consulting the documentation for this solution, there is very little in the way of describing how the above endpoints are to be used. Furthermore, they are not a part of the Confluence Rest API documentation (found here: https://developer.atlassian.com/cloud/confluence/rest/v2/intro), and this page also has no mention of any way to create a backup through the REST API. Some user made forum posts reference the above requests that we are using, but they are from older posts. Newer ones suggest there is no support for preparing these backups programatically. As a result, we have a couple questions related to this process:
Is this route of using the above '/obm/' requests the intended solution of scriting a backup of all of our Confluence data, despite not being mentioned in official REST API documentation?
Is there documentation available for the above requests that are accessible to the public, with examples of how the above requests are to be used, and what their response syntax looks like?
If the above solution is not intended, is there a solution that leverages the REST API that we can use to recreate what we once used?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.