Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-53343

With the move to Filestore, customers are unable to see which backups were created previously

      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:

      1. 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)
      2. 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"
      3. 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)

            [CONFCLOUD-53343] With the move to Filestore, customers are unable to see which backups were created previously

            Sunny Xu (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            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!

            Sunny Xu (Inactive) added a comment - 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!
            Li Hsu (Inactive) made changes -
            Labels Original: affects-cloud New: affects-cloud stale-bulk-close
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2363574 ] New: JAC Bug Workflow v3 [ 3420340 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 32 New: 33
            SET Analytics Bot made changes -
            Support reference count Original: 6 New: 32
            SET Analytics Bot made changes -
            Support reference count Original: 32 New: 6
            SET Analytics Bot made changes -
            Support reference count Original: 31 New: 32
            SET Analytics Bot made changes -
            Support reference count Original: 32 New: 31

            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

              mgoldman@atlassian.com Mariano Goldman (Inactive)
              fsim Foo Sim (Inactive)
              Affected customers:
              7 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: