Hi all,
I am running Jira out of the Atlassian Docker-Container in Version 8.6.
I want to have backups writen to backup share on my Synology. The share is mounted as a volume in the Docker Container to /JiraData/.
In that Folder I created a folder /export/.
In the Jira folder var/atlassian/application-data/jira/ I created a symbolic link 'export' to /JiraData/export.
I gave the Jira User all permissions to read an write, I can cd into the symbolic link @var/atlassian/application-data/jira/export and see all file my filemanager shows me.
But if I want to create a Backup in Jira I get this message:
Unable to save the backup file '/var/atlassian/application-data/jira/export/test.zip'.
Any idea how to fix that?
Since you are using docker, there may be chance that one day attachments may also get big in size and you will decide to move them too!
So mount the disk of size based on your Jira instance and how may it grow in future (Permissions of are jira user in linux instance is important)
Then change the home directory.
If you do not want the changing directory option, there is another option available, to save the backup you still need to mount the disk with permissions related to jira user (much important) and move the backup from export folder to the disk with cron job.
Hi @Mirko
It is not possible to change the backup location.
Instead, I will suggest you use a system based tool based on a cron technology to copy it at regular intervals.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And why is that? It would be convenient the have the Backups exported to a versioned share... Even more if there was an interface to choose the backup target!
What cron service would be recommended?
I'm not a programmer and am a bit annoyed that the majority of issues here has to be solved via the command line. I didn't buy a finished product to mess around with cmd for hours only to run in the next 'issue'.
Sorry, but this is really not very practical!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why is that?
Sorry I cannot answer this as I do not work for the vendor, hence not privy to decisions of this nature and you could always raise a suggestion at jira.atlassian.com for such a feature.
That all depends on what operating system and whom you system admin is.
Ask the person to do the following:
Do test this on a staging instance first before attempting on your production.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.