This feature request was originally opened for Cloud (on-demand)

+1 !

Automate backup, just need to implement in Jira cloud. If you critical question of disk space, you can limit Auto Backup a week or a few days. The absence of the process of creating automatic backups puts my business at risk.

This looks to be an old issue, but I am new to JIRA administration, so I figured I would add my two cents.

Not having the ability to do automated scheduled backups really drives home how unready JIRA Cloud is for enterprise use.

For our on site systems we have backups going back years. While we don't need them often we do use them to save hundreds if not thousands of man hours when a system fails or someone makes a big mistake.

I'd go one step further on this and say that not just the generation but the offsite dumping of the data should be done by JIRA/Atlassian Cloud. Otherwise you still have to run a server to download the dump off WebDAV nightly, which seems to defeat the purpose of paying Atlassian to avoid administering servers. Unfuddle can do automated nightly dumps of data to S3; having a similar feature for JIRA would make a lot more sense than having to run backup generation/downloading scripts ourselves.

It just strikes me as rather odd that even though the entire point of paying for JIRA OnDemand is not to run your own servers, you still have to run, maintain, and check on your own server to run backups. If we wanted to do that, we'd already be running and sysadmining our own JIRA instance anyways - and for smaller nontechnical organizations that might want to use JIRA, maintaining a backup server in-house is out of the question anyways.

Agreed - this functionality, as a system administrator, is very important.
Atlassian needs to keep in mind that its customers might have to follow strict Government guidelines on data retention, and this should also be taken into account when providing a backup solution. Right now, the backup facility just doesn't 'cut the mustard'!

The restrictions applied to backup frequency could also be an issue - 48 hours per backup and retention time of backups on WebDav is only 24 hours, Why?

Ideally, it would be great if Atlassian provided the backup functionality as a service. ie. You just set your preferred backup period, and Atlassian will store your backups for you (on WebDAV).
Obviously there will be a limit of the number of backups, ie. Atlassian will only retain the last 24 backups. Customers can find the best period that suits them (they may want to be able to restore as far back as 2 years, so they choose a monthly backup, other customers may want to be able to granularly restore on a set day so the trade-off is they can only go back as far as 24 days).
Another option is to keep allowing customers to download backups from WebDAV so they can have the 'granular' restore option but also keep historical backups dating past the 24 day limit by downloading from WebDAV every 20 days (or so).

It is very important to have this functionality

An additional component of this request could be to adjust the backup frequency to extend beyond the current webdav retention period of 24 hours.

Hi,

I think this should be a priority to allow users to implement their own disaster recovery plans while using OnDemand. At the moment backups are a manual process which leads to risk as these could easily be missed.

Regards,
Tony

Please raise the priority of this issue so that it gets some attention.It should be fairly easy to automate this process .