How to redirect System Backups from the /export/ to different target

Question

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?

Pramodh M · Answer

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.

Mirko_axd7uu · Answer

Thank you for your explanations!

Ismael Jimoh · Answer

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:

* Create a cron job on the operating system with something like cp /pathtobackup /pathtonewstorage (you can improve this by adding a date checker to ensure only the latest ones created that day are copied or even those from the day before)
* Add a time that is roughly after your backup say if your backup service runs at 1 am each day and you know it ends after 20 minutes, then trigger your copy at 1:30am

Do test this on a staging instance first before attempting on your production.

Cheers.