-
Bug
-
Resolution: Timed out
-
Medium
-
33
-
Severity 2 - Major
-
Summary
Previously, It's possible to navigate to CloudURL/webdav/backupmanager to see which backups have already been created previously. With Filestore, that's no longer possible. This creates a few issues:
- Only the person that generated the backup are able to download the generated backup (other users will not be able to, they will need to re-generate it again)
- Another user might wish to generate the backup shortly after that, but instead, is faced with this: "Backup frequency is limited. You can not make another backup right now"
- Previously usable backup scripts are broken, especially those that automatically downloads the backups from /webdav/backupmanager (which was a much neater way of doing things)
- is related to
-
CONFSERVER-45003 Document How Confluence Backup Works With The New FileStore (No longer stored at /webdav/backupmanager, and saved only as Site_Backup.zip)
- Closed
[CONFCLOUD-53343] With the move to Filestore, customers are unable to see which backups were created previously
Terrance Teoh
added a comment - After I got my Atlassian ID verified, I was told to run this curl command.
And it seems to work.
curl -D- -u <JIRA email>:<JIRA password> -X GET https://<your site>/rest/api/2/myself
However the Python script is still getting a:
Triggering backup
Trigger response: 401
Trigger failed
Terrance Teoh
added a comment - After I got my Atlassian ID verified, I was told to run this curl command.
And it seems to work.
curl -D- -u <JIRA email>:<JIRA password> -X GET https://<your site>/rest/api/2/myself
However the Python script is still getting a:
Triggering backup
Trigger response: 401
Trigger failed
I was looking at this last week. I'm busy updating the python script to use REST based authentication.
Will publish it as soon as it's tested and working.
Terrance Teoh
added a comment - Hi Antony,
Thanks for answering ! 
I think I need to verify my Atlassian ID. There is an error when I tried, and I have raise a ticket with their Support Team.
I found similar issue with other groups here: https://support.aha.io/hc/en-us/articles/115002476386
Terrance Teoh
added a comment - Hi Antony,
Thanks for answering !
I think I need to verify my Atlassian ID. There is an error when I tried, and I have raise a ticket with their Support Team.
I found similar issue with other groups here: https://support.aha.io/hc/en-us/articles/115002476386
Everyone was moved to an Atlassian ID so that may be the issue. Not sure about Python, but with Powershell we also had to adjust the authentication slightly. Discussion here: https://bitbucket.org/atlassianlabs/automatic-cloud-backup/issues/10/powershell-script-was-working-but-now
Terrance Teoh
added a comment - The Python script used to work fine.
But lately I am getting:
Triggering backup Trigger response: 401 Trigger failed
I tried changing -u from Username to Email Address.
But that did not help.
Any ideas ?
Thanks !
Terrance Teoh
added a comment - The Python script used to work fine.
But lately I am getting:
Triggering backup
Trigger response: 401
Trigger failed
I tried changing -u from Username to Email Address.
But that did not help.
Any ideas ?
Thanks ! I've been granted permission to make this public:
https://github.com/MyMedsAndMe/jira-confluence-backup
I've been asked to keep this private for the moment - will let you know when it's available.
I've published this to github:
https://github.com/MyMedsAndMe/jira-confluence-backup
webcapcha webcapcha
added a comment - Yes, I'm interesting in this script.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!