Automated backup supported or not

[Aaron Hicks]

Some pages say the automated/automatic backup/export scripting is not supported, other pages say it is, can this page be updated to be more specific please?

Since I could not comment on an answer to the question below(comment editor never completes loading), I updated the question.

Please refer to https://confluence.atlassian.com/jirakb/removal-of-webdav-directory-support-for-jira-cloud-instances-859477758.html

When you click at the bottom to see questions on that page you will see this question - Hence the number 859477758 in the tag for this question. it associates it to that page. My question relates to that page. (It links from page to question but there seems to be no way to link from question back to page?)

At the time of writing this page states: "Automated exports for backing up your data
JIRA Cloud has supported automatic backup file creation and download via a private API and the automatic-cloud-backup script from Atlassian Labs. We have made changes to this script to support the new JIRA Cloud backup mechanism. To continue creating automatic backups, download the updated script from Bitbucket."

This paragraph includes the phrases "Automated exports for backing up your data" and "automatic backup file creation" and "automatic-cloud-backup script" and "automatic backups".. My words "automated backup" refer to these phrases.

It is clear that Atlassian supports the underlying mechanism for doing exports. It is also clear that the sample scripts for using the API for accessing it is not directly supported by Atlassian. In places the API is referred to as "private" and I could not find API reference documentation. What is unclear is whether the API exposed by Atlassian for such exports is a formal public API that is documented and supported. Can people make plans with the assumption the API will remain and be supported or are we at risk that the API is experimental and might be discontinued?

My question is whether what this page and this paragraph refers to is supported by Atlassian or experimental. This page implies it is formally supported when it says "JIRA Cloud has supported automatic backup file creation and download via ...",

My request is that you update the documentation to remove ambiguity as to what is a formally supported and documented feature and what is experimental and used at customer's own risk.

Regards

Ruan

[darylchuah]

Hi Fabby

I guess you have bump in to this situation : OutOfMemory Error or Poor Performance due to XML Backup

Please try the suggested resolution which could possibly address your issues.

Hope it helps

Cheers :)

[fabby]

thanks DaryI

to be on the safe side,i both use a native database tool and XML bakckup as a backup strategy

[Paul Stahlke]

I just upgraded from JIRA 6.1.7 to 6.3.15 yesterday, and it seems that the backup service has been disabled on startup.  It now appears to run on a strict schedule based on the interval you set.  Mine runs every 120 minutes, so I have backups for 6:09, 8:09, 10:09, etc.  I even restarted the system in between, and it appears to remember the last backup and when the next one should run.

[Heshan Manamperi]

Are u running JIRA on linux or windows?

What is the memory configurations? Alocate to JIRA?

[fabby]

Windows Server 2008 R2 Enterprise 64 bit ,its physical configuration is as follows,

CPU:Intel(R) Xeon(R) E5520 @2.27GHz 2.26GHz

RAM: 12GB

and has allocate Xmx 1024m to JVM.

[Heshan Manamperi]

Daryl is correct. you have to increase memory for heap and JVM.