can a shared NAS be used as the attachments path?

I have two production linux servers that connect to the same Oracle 10 database. The servers are running v4.1#519.

Server A is actively used and it's drive space (8gigs) is nearly exhausted due to all the attachements.

Server B is more or less a standby server it connects to the database and can reference all the issues but not the attachements uploaded by users.

I am having a shared NAS storage area created with 70 gigs of space.

Am I safe in changing the attachements path of both servers to point to the shared NAS server?

2 answers

1 accepted

0 votes
Accepted answer
Having attachments folder on a NAS filer is safe if you make sure that you use different paths on the NAS filer for all Jira instances that access the NAS share concurrently

One attachment folder on a NAS should always be used exclusively by one server. If you know that both servers run concurrently and write into the same folder you will not know anymore to which Jira the folders for the individual projects belong too. That might be important if you want to create a backup for an instance with all associated attachments

But if the second server runs a standby instance which only comes into play when the first server crashes it's a perfect setup if the standby instance is configured to use the same attachment path.

in this setup the standby server should be comfigured identical to the primary and also use the same data in it's database as the primary. This could be achieved by continuously replicating the database from the primary to the standby server or by using a dedicated separate database server accessible by both servers or by local database servers using data files on a shared SAN disk which has access paths from both servers. The latter is likely a solution you will find in large data centers

0 votes
Stefan Broda Atlassian Team Jun 05, 2012

For more file replication options for JIRA home and installation directory:

Atlassian has just released a dedicated best practice guide for High Availability. It covers a cold failover scenario and includes implementation details on reverse proxying, monitoring, replication and failover mechanisms:

Suggest an answer

Log in or Sign up to answer
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

63 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you