What is the first step to perform a rollback to a previous Confluence version?

What is the first step to perform a rollback to a previous Confluence version?

• A. Start Confluence and rebuild the search index.
• B. Update the confluence.cfg.xml to point to the correct database and copy over the attachments folder.
• C. Delete the current database and start fresh.
• D. Install a new clean Confluence of the version that needs to be restored and restore the database backup (from before the upgrade).

Answer: (D)

The first step in rolling back is to bring the system back to the state that matches the older version you want to restore. This means installing a clean instance of Confluence that matches the target older version and then restoring the database backup taken before the upgrade. Doing this ensures the application code and the data schema are aligned, avoiding schema or compatibility issues that would occur if you tried to run the older data on a newer binary or mix in the wrong components. After the older version is installed, you would then restore the pre-upgrade database (and the attachments/home content) to complete the rollback. Starting Confluence and rebuilding the index, pointing the current instance at a different database, or deleting the current database would not correctly revert the upgrade and could lead to data loss or instability.

The first step in rolling back is to bring the system back to the state that matches the older version you want to restore. This means installing a clean instance of Confluence that matches the target older version and then restoring the database backup taken before the upgrade. Doing this ensures the application code and the data schema are aligned, avoiding schema or compatibility issues that would occur if you tried to run the older data on a newer binary or mix in the wrong components. After the older version is installed, you would then restore the pre-upgrade database (and the attachments/home content) to complete the rollback. Starting Confluence and rebuilding the index, pointing the current instance at a different database, or deleting the current database would not correctly revert the upgrade and could lead to data loss or instability.