In our company we run a confluence 5.5.6 with 130.000 users and over 250.000 active pages in 2.200 pages. We often experience scaling issues and we doubt if we reach a critical level of users / content one day and confluence will stop working properly. Therefore, we think about splitting our confluence instance in several instances like we already did with JIRA.
Atlassian offers some documentation and best practices about splitting a JIRA instance but not for a confluence instance, like: https://confluence.atlassian.com/display/JIRA/Splitting+a+JIRA+instance and https://confluence.atlassian.com/display/ENTERPRISE/Federating+JIRA+-+Managing+Multiple+Instances
Are there any Best Practices for managing multiple confluence instances known? Does someone has experience on this? We think that splitting a confluence instance could get very difficult.
For Confluence, you can do the same as the JIRA page states above. Instead of projects, replace as spaces.
However there is a difference. Confluence doesn't work very well with XML backups when they are very big, so I recommend to use a database backup dump to clone the instance to another one and then just delete the spaces which you don't want to be in the second instance. The process to clone the instance is this one.
Just note that to run 2 production instances of Confluence, you'll need 2 active licenses.
I hope this helps!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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!
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