-
Suggestion
-
Resolution: Unresolved
-
49
-
-
Jira Software
Issue Summary
When you have an instance with a large storage usage of attachments, say 1TB+, it is currently impossible to create and export the full backup (including attachments) from Cloud. It is only possible to export it without attachments.
Steps to Reproduce
- In an instance with large storage usage, go to the Back up manager , under Back up for cloud, check the box "Include attachments, avatars, and logos in the backup".
- Select "Create backup for cloud"
Expected Results
The backup may take hours or days (depending on the storage usage), and it is comprehensible due to its sheer size, but it will eventually finish, and you'll be able to download it.
Actual Results
After hours or days (depending on the storage usage), the following error will be thrown:
Workaround
It is not the ideal solution, but a sandbox instance could be used as a backup*, you would need to create a sandbox and then use the 'Copy production data' https://support.atlassian.com/organization-administration/docs/manage-product-sandboxes/#Copy-data-to-a-sandbox
*Note that there are some components that are not copied to the sandbox.
[CLOUD-11743] Support full backups with attachments for instances with large storage usage
As Nate and Aleksandar said, if something catastrophic happens, without backup, we are vulnerable and it also reduces reputation of Jira / Confluence.
Having Sandbox as a backup or backuping without attachments are better than nothing but these options are not real / full backups. Sandbox doesn't have all what prod env has, and data in attachments are also part of Jira / Confluence and sometimes very important for our users.
The workaround here may not even be feasible for us as well. Like Nate mentioned above, our company also requires a similar backup strategy. We need to be able to download a full backup and have it ready offsite in case something catastrophic happens to our current Jira instance. This limitation is noted nowhere else but here, which is scary to think about because it leaves us vulnerable and without proper backups but it's not advised.
The suggested workaround is not feasible. We need a legitimate backup solution. Using the sandbox for a backup solution does not work because we have numerous teams using it for sandbox / pre-production purposes. We are already on a 12 week rolling cadence to refresh our sandbox to limit impact on teams that are utilizing it. We need the ability to backup and optionally rollback to a date up to a week in the past, should there be something catastrophic that happens, among other reasons.
Backup solutions are business-critical in any domain. If the tool can not be offered quickly due to the complexity, please allow us, at least, to create multiple "backup" sandboxes.