Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Disaster Recovery Configuration for Jira and Confluence

I am planning on setting up a cold standby DR server to mirror our Confluence and Jira server. The filesystem will be fully replicated as well as the databases. However, I have a few configuration questions.

The base url will not need to be changed, correct? As long as the DNS record points to the new DR server all links should redirect. I don't wan't to have to worry about configuration files pointing back to the production site somehow.

Does the server id need to be changed? Same with the license?

It looks like application inks should be fine as well. But I noticed when using Jira as the User Server for Confluence, Fisheye, etc. that they are configured by IP. Can a url be used instead? Otherwise these will fail.


1 answer

1 accepted

2 votes
Answer accepted

Correct on the base url. Check your hosts file on the replicated server though.

For the server ID, cheat. Install the development license you're entitled to on it instead of the real licence and it'll work fine with a different server ID. Disaster recovery/failover is one of the things your dev licence is intended for. This also makes failing back a lot more simple too, as there's no fooling around with server IDs!

Ah, no, application links explicitly rely on IP addresses, so you'll need to change them. In fact, they do work with urls, but not very well in my experience. I tried it on a test system, and noticed slowness (to the point of timeouts), gave up and went back to raw IPs. This was with an older version of Jira, but I don't think it will have changed much (Which reminds me, I need to test this stuff with IPV6 soon...)

+1 for that Application Links part. It's a bit messy around that and it will mostly fail. You will have to recreate it.

Confluence has builtin clustering capabilties - check out

Functionality will remain the same with the dev license? Will licensed plugins still work? Thanks!

I can't speak for the plugins, but Jira, Confluence, Greenhopper etc will work fine with a dev license. I've not yet found a plugin that objects, I think they may look at the license state of the system they're installed in.

Suggest an answer

Log in or Sign up to answer