Upgrade from 7.11.2 to 8.5.4

Gurbir Kaur February 15, 2024

We are upgrading from Confluence DC 7.11.2 to 8.5.4 and from SQl 2016 to SQL 2019 .

source 4 nodes running on 7.11.2 and destination 5 nodes  to 8.5.4.

We will be restoring Db from 2016 to 2019 with compatibility mode set to 2016. On the destination we will be running 7.11.2 and after DB restore and NAS Sync we will do an upgrade to 8.5.4(by changing the symbolic link of install) followed by re-index.


My question is do shall we do a re-index when we restore onto 7.11.2 or directly perform a re-index after upgrade ?

1 answer

1 vote
Kian Stack Mumo Systems
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2024

@Gurbir Kaur

If I'm understanding what you are saying, you should not need to re-index after upgrading the DB, but only after upgrading the instance to the 8.5.4 version.


If you look at the documentation for migrating a DB (not quite the same, but close enough) there is no need to perform a re-index as the index files are kept on the file system.

Gurbir Kaur February 16, 2024

Sorry just to add, we are not only migrating DB but App servers as well from .

I mean the whole env is moving from VMC1 to VMC2 in which it will from SQL 2016 to SQl 2019.

So before upgrading from 7.11.2 to 8.5.4, should be run a re-index from scratch at 7.11.2 ?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events