Upgrading Confluence Data Center
This page contains instructions for upgrading an existing Confluence cluster.
If you are not running Confluence in a cluster, follow the instructions in Upgrading Confluence.
If you're running Confluence in a cluster in AWS, follow the instructions in Running Confluence Data Center in AWS.
In this guide we'll use the following terminology:
- Installation directory – The directory where you installed Confluence.
- Local home directory – The home or data directory stored locally on each cluster node (if Confluence is not running in a cluster, this is simply known as the home directory).
- Shared home directory – The directory you created that is accessible to all nodes in the cluster via the same path.
Currently using Confluence Server? Learn more about the benefits of Confluence Data Center.
On this page:
1. Back up
We strongly recommend that you backup your Confluence home and install directories and your database before proceeding.
More information on specific files and directories to backup can be found in Upgrading Confluence.
2. Download Confluence
Download the appropriate file for your operating system from https://www.atlassian.com/software/confluence/download
3. Stop the cluster
You must stop all the nodes in the cluster before upgrading.
We recommend configuring your load balancer to redirect traffic away from Confluence until the upgrade is complete on all nodes.
4. Upgrade the first node
To upgrade the first node:
- Extract (unzip) the files to a directory (this will be your new installation directory, and must be different to your existing installation directory)
- Update the following line in the
<Installation-Directory>\confluence\WEB-INF\classes\confluence-init.propertiesfile to point to the existing local home directory on that node.
- Copy the jdbc driver jar file from your existing Confluence installation directory to
confluence/WEB-INF/libin your new installation directory.
The jdbc driver will be located in either the
- If you run Confluence as a service on Windows, delete the existing service then re-install the service by running
- Copy any other immediately required customizations from the old version to the new one (for example if you are not running Confluence on the default ports or if you manage users externally, you'll need to update / copy the relevant files - find out more in Upgrading Confluence Manually)
- Start Confluence, and and confirm that you can log in and view pages before continuing to the next step.
You should now stop Confluence, and reapply any additional customizations from the old version to the new version, before upgrading the remaining nodes.
5. Upgrade Synchrony (optional)
If you've chosen to let Confluence manage Synchrony for you (recommended), you don't need to do anything. Synchrony was automatically upgraded with Confluence.
If you're running your own Synchrony cluster, you should:
- Grab the new
<local-home>directory on your upgraded Confluence node.
- Copy the new
synchrony-standalone.jarto each of your Synchrony nodes, and start Synchrony as normal.
6. Copy Confluence to remaining nodes
The next step is to replicate your upgraded Confluence directories to other nodes in the cluster.
- Stop Confluence on the first node.
- Copy the installation directory and local home directory from the first node to the next node.
If the path to the local home directory is different on this node, edit the
confluence-init.propertiesto point to the correct location.
- Start Confluence, and and confirm that you can log in and view pages on this node.
- Stop Confluence on this node before continuing with the next node.
Repeat this process for each remaining node.
7. Start Confluence and check cluster connectivity
Once all nodes have been upgraded you can start Confluence Data Center on each node, one at a time (starting up multiple nodes simultaneously can lead to serious failures).
The Cluster monitoring console ( > Clustering) includes information about the active cluster nodes. When the cluster is running properly, you should be able to see the details of each node. > General Configuration