Can JIRA backup be made exactly every 48 hours?

[James MacEwan]

It is early days for us with JIRA and I would like to backup JIRA frequently as we are regularly making configuration errors and similar. I plan to automate JIRA backups using crontab expressions. The less timing logic I need to put into my scripts the better.

After a backup is made, is the next backup allowed to be made 48 hours from the start of the previous backup or from the end of the previous backup?

How strongly enforced is the 48 hour timeframe? If I start a backup 47 hours, 59 minutes and 58 seconds after the previous backup, will it fail?

[Mirek]

48h limit is only for backups with attachments. You script can run data backups more often and once a time do a bigger backup with all attachments for example on a weekend. Data backups can be executed without any delay.

To not care about the exact limit time your script can look at the backup progress or check if a new backup can be executed. So you run script exactly every 48h in cron but the script is checking if backup could start. You probably would get an error when the limit is there, so you script would need to handle it.

Please look (for inspiration) at the sample scripts located here

https://bitbucket.org/atlassianlabs/automatic-cloud-backup/src/d43ca5f33192e78b2e1869ab7c708bb32bfd7197/backup.ps1?at=master&fileviewer=file-view-default

[James MacEwan]

Thanks for the advice. I was hoping to have zero timing logic in my scripts but it seems unavoidable.