How to disable upgrade recovery file generation in Confluence
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
By default, Confluence creates an upgrade recovery file before and after an upgrade. This file can be used to roll back if your upgrade fails. However, generating this file can take long time on sites that are medium sized or larger, and can be safely turned off if you have a robust process to back up your database and verify the backup before performing an upgrade.
It's important to note that if you disable the upgrade recovery file, and your upgrade fails, you will need to rely solely on your database and file system backups to recover from the problem.
Solution
To disable the upgrade recovery file:
- Stop Confluence.
- Set the
-Dconfluence.upgrade.recovery.file.enabledfalse
The way you do this will depend on how you run Confluence. See Configuring System Properties to find out how to set system properties in your environment. - Restart Confluence.
If you're running Confluence in a cluster, you can make this change to each node in turn, you do not need to stop all nodes at once.
Remember that this property must be set before you begin the upgrade. If you upgrade Confluence manually, that means updating this property in the setenv.sh or setenv.bat file in the install directory of the version you are upgrading to, not just your current install directory.