Help to find best Confluence upgrade path: v6.5.0 (link to JIRA v6.3.1 internal database) to v16.5.1

[Alexandra Micallef]

Hi, 

Our setup for JIRA and Confluence was as follows: 

- JIRA (6.3.1) with internal database

- Confluence (6.5.0).  Confluence was configured to share JIRA users - it was linked to JIRA's internal database to pick up user access information.

- Both running on the same Windows server.

We performed the first leg of our upgrade on our JIRA instance in the following manner (this is right now our current setup): 

- JIRA (7.11.2) with external database running on the same CentOS (MySQL)

- Confluence remained on the Windows server still connected to the JIRA (6.3.1) internal database

We next require to upgrade our Confluence to version 6.15.1.

Can you please inform us of the best upgrade path to adopt and execute?  The following are the options we have painted out - but we are not sure which is the best approach to take: 

option 1) Upgrade to Confluence (6.15.1) keeping it attached to JIRA (6.3.1) internal database on the windows server

option 2) Upgrade to Confluence (6.15.1) utilising an external database on a CentOS (MySQL) machine - same approach we took for our JIRA setup upgrade

option 3) Upgrade to Confluence (6.15.1) utilising an external database on Windows.  Then migrating Confluence and external database to CentOS.

Are there any other better options to consider? 

Regards,

[Alexis Robert · Accepted solution]

Hi @Alexandra Micallef , 

the best option from my experience would be number 2: you get all your applications on the same database (so less maintenance on your side), and you can follow the same migration path than you did for Jira.

The internal database should really only be used for demo or testing, no for production purposes.

Let me know if you have any questions, 

--Alexis

[Alexandra Micallef]

@Alexis Robert Thank you for your advice.  We will plan according to option 2.  If we encounter any issues or queries i will drop you a message for further advice - thank you