nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA redundancy

Nir Mishal

today we have one JIRA server and one SQL server for the JIRA .
we looking to create two JIRA servers that will point the same SQL server and the two JIRA must be sync between them - when the user will open the JIRA in each server he will see the same data and he can create ticket on both servers.

Atlassian JIRA Project Management Software (v6.3.15#6346-sha1:dbc023d)

what is our options ?

thanks,

nir.

Accepted answers

Nic Brough -Adaptavist-

There are no options. You can't do it. You can only have one active JIRA server.

Unless you buy the data centre version of JIRA, but that still isn't quite what you describe.

All comments

Nic Brough -Adaptavist-

There are no options. You can't do it. You can only have one active JIRA server.

Unless you buy the data centre version of JIRA, but that still isn't quite what you describe.

Daniel Wester

The requirement doesn't make sense. Why not just replicate the database to a different server and then rsync the attachments every couple of hours. What exactly are you trying to accomplish?

Like Nic said - Data Center might be an option for HA.

Nir Mishal

We need two JIRA servers – one JIRA in one network and second JIRA in one network and both of them will point to same DB server , No matter which JIRA server the user will connect he will get same data .

JIRA1 – 192.168.15.16

JIRA2 – 192.168.18.16

DB server 192.168.17.16

Please let me know what is our options ?

Thanks again ,

Nir.

Silviu Burcea

AFAIK, JIRA Data Center will do the sync between JIRA instances for you. The only downside is that you need 1 license per JIRA instance.

Nic Brough -Adaptavist-

It is the SAME answer. You cannot do this with plain JIRA JIRA Data centre will get you close, but it is the only option that will do anything like what you want.

David Dunaway

How about Active/Slave site setup?

Active site replicates DB to slave site.

Use load-balancer to point to active site until it fails. then direct traffic to slave site.

Slave site is not available to users unless Active site fails

Anyone try that approach?

Nic Brough -Adaptavist-

Many of us. Of course, the slave site has to be shut down - on failover, you will need to make the slave database read/write, start JIRA and re-index it.