Migrate H2 database
Bitbucket Server upgrade guide
On this page
In this section
Related content
- RejectedExecutionException
- Webhook events are skipped because the queue is full
- Application metrics reference
- Diagnostics for third-party apps
- Hazelcast network partition causing Plugin Issues in Bitbucket Data Center
- Hazelcast network partition causing Plugin Issues in Bitbucket Data Center
- SpringMVC dispatcher springMvc could not be started due to AccessDeniedException on Windows.
- Bitbucket fails to start up with Hazelcast instance is not active error
- Bug fixing policy
- Bitbucket Data Center freezes after upgrading from 7.x.x to 8.x.x
The H2 database can’t automatically migrate your data during the Bitbucket upgrade. That’s why a Bitbucket admin should migrate the data manually to the upgraded Bitbucket instance.
If you’re upgrading from:
- Bitbucket 8.8 to Bitbucket 8.8+, you don’t need to do anything.
- from versions below 8.0 to Bitbucket 8.0-8.7 (for example from 7.19 to 8.2), you’ll need to migrate your data to the MvStore format. Learn how to migrate H2 database from 1.3 to 1.4
- from versions below Bitbucket 8.8 to Bitbucket 8.8+ (for example from 8.0 to 8.8 or 7.21 to 8.9), you’ll need to migrate your data from version 1.x (for example 1.3.176 or 1.4.200) to version 2.1.214. Learn how to migrate H2 database from 1.x to 2.1
Last modified on Jan 31, 2023
In this section
Related content
- RejectedExecutionException
- Webhook events are skipped because the queue is full
- Application metrics reference
- Diagnostics for third-party apps
- Hazelcast network partition causing Plugin Issues in Bitbucket Data Center
- Hazelcast network partition causing Plugin Issues in Bitbucket Data Center
- SpringMVC dispatcher springMvc could not be started due to AccessDeniedException on Windows.
- Bitbucket fails to start up with Hazelcast instance is not active error
- Bug fixing policy
- Bitbucket Data Center freezes after upgrading from 7.x.x to 8.x.x
Powered by Confluence and Scroll Viewport.