Question
Confluence backup and restore: diagnosing recovery path after failed upgrade
Zo Indigo
0 reputation · 18 Mar 2023, 13:54 UTC
126.3K views1
Loading…
0 reputation · 18 Mar 2023, 13:54 UTC
Diagnose whether to restore pre-upgrade Confluence backups or attempt forward repair after an upgrade fails to complete.
Downgrading Confluence after database schema migration is generally unsupported. Data Center rolling upgrades can leave cluster nodes on different versions, while Server upgrades affect one node. Restoring requires database and home-directory backups from the same point in time; mismatched copies risk corruption. Residual upgrade markers or lock files may also block startup.
No specific failure is assumed. The choice depends on backup completeness, cluster topology, and whether migration finished.
Should pre-upgrade backup validation determine the restore-versus-repair decision? How does a split cluster version affect restore scope? What indicates that upgrade markers or lock files must be cleared before restart?
Downgrading Confluence after a database schema migration is generally unsupported and highly risky.
The decision hinges on the completeness of the pre-upgrade backup validation and the state of the cluster (single node vs. Data Center rolling upgrade).
To refine the recommendation, confirm the exact state of the cluster: Was this a single-node Server upgrade or a Data Center rolling upgrade?
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.
confluence