Confluence Docs 3.0 : Confluence Cluster Installation with Existing Data This page last changed on Sep 07, 2009 by ggaskell. ### Overview There are two methods of installing Confluence in a cluster, depending on whether you have existing data. This page describes how to upgrade an existing Confluence instance into a cluster. See also Cluster installation without existing data.
| Oracle Coherence Licensing Change: Due to a license agreement change between Atlassian and Oracle over the Coherence technology, from September 2009, Confluence will be made available in two editions: Standard Edition — Confluence with Ehcache's caching technology (available to customers with non-clustered Confluence licenses). If you are currently running a clustered installation of Confluence, please do not upgrade it with a standard edition of Confluence. Clustered Edition — Confluence with Oracle's Coherence clustering and distributed caching technology (available to customers with Confluence clustered licenses only). For more information about these changes, please refer to the Coherence License Changes document. If you have a Confluence clustered license, are running a clustered installation of Confluence and wish to upgrade to Confluence version 2.6 or later after late September 2009, please ensure that you download only a clustered edition of Confluence and please refer to the Confluence 3.0.1 Upgrade Notes for additional upgrade information.
### Cluster installation from an existing copy of Confluence To upgrade an existing copy of Confluence to run in a two-node cluster, you must do the following: Ensure that your standalone version of Confluence has been upgraded to the version you want to run the Cluster on. Do not upgrade your version of Confluence and switch to the clustered version at the same time. First upgrade your system (e.g. from Confluence 2.5.8 Standalone to 2.7.1 Standalone) and make sure everything works fine (e.g. for a week) before switching (e.g. from Confluence 2.7.1 Standalone to 2.7.1 Clustered) Ensure you meet the clustering requirements, including obtaining a clustered license key from Atlassian for each node Due to CONF-8959, you need to perform attachment migration to the database before you change your license to a clustered license Upgrade the existing Confluence instance to a clustered license Enable clustering and select a cluster name Shut down the first node, copy the Confluence application and Confluence home directory to the second node Start the first node, wait until it is running, then bring up the second node and it will automatically join the cluster Test the cluster is working correctly Configure a load balancer in front of the two clustered nodes. Each of these steps will be described in detail below. ### 1. Clustering requirements Your Confluence cluster installation must meet all the following criteria for clustering: you must be running Confluence 2.3 or later you must have a clustered license you must use an external database you must use a load balancer with session affinity in front of the cluster. Clustered commercial licenses may be purchased through Confluence website. Clustered evaluation licenses may be obtained by emailing sales@atlassian.com. A cluster can run using two copies of Confluence Standalone. However, cluster administrators must understand how to configure an application server and web server with load balancing, so we recommend you are comfortable installing Confluence as a EAR/WAR in your application server before proceeding with a clustered installation. You can follow the instructions to Migrate Confluence to an external database. ### 2. Upgrade existing instance to clustered license Once you've obtained your clustered license from Atlassian, you can simply update the license in your running Confluence instance: Go to 'Administration'. Go to 'License Details', and paste in the new license. Click 'Save'. When you enter a clustered license, you will see a new line appear on this page: Licensed Clustered Nodes. This tells you how many nodes your Confluence license will allow. License Details page shows the number of cluster nodes permitted ### 3. Enable clustering and select a cluster name When you change Confluence to use a cluster license, a new menu option will be revealed on the left: Cluster Configuration. Open this menu item to configure your cluster. On this page, you need to enter a name for your cluster, and possibly select which network interface on your server will be used for the cluster (only if you have more than one suitable interface). Clicking 'Start cluster' will migrate your attachments to the database, then prevent any access to Confluence until it is restarted.
| Technical note The cluster name will be converted into a unique multicast IP address and port for your Confluence cluster. UDP multicast traffic is used for Confluence to automatically discover other nodes in the cluster when they start up.
### 4. Copy Confluence to second node For the remaining steps in setting up a cluster with existing data, please continue from step 4 in the normal Confluence cluster installation guide. ### 5. Start Confluence on the first node, wait, then start Confluence on second node See comment in step 4. ### 6. Test cluster connectivity See comment in step 4. ### 7. Configure load balancer See comment in step 4. ### Troubleshooting If you have problems with the above procedure, please see our Cluster Troubleshooting guide. ### Upgrading a cluster It is important that upgrades follow the procedure for Upgrading a Confluence Cluster. ### Related documentation Overview of Confluence Clusters Confluence Cluster Installation Confluence Installation Guide Upgrading a Confluence Cluster Confluence User Guide Attachments: licenseDetailsCluster.png (image/png)

Document generated by Confluence on Nov 05, 2009 23:27