Migrate H2 database
Bitbucket Data Center upgrade guide
On this page
Related content
- Possible Confluence and Synchrony Configurations
- Running Confluence behind NGINX with SSL
- Using Apache with mod_proxy
- Running Confluence Over SSL or HTTPS
- Confluence Collaborative Editing does not work with SSL and Apache 2.4.9 or earlier
- How to check if Confluence is accessible from the internet
- Can't check base URL warning in Confluence 6.1 or later
- Collaborative Editing error in Confluence Data Center due to blocked mixed content
- Configuring Web Proxy Support for Confluence
- How to use NGINX to proxy requests for Confluence
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.x and later
Last modified on Aug 7, 2023
Related content
- Possible Confluence and Synchrony Configurations
- Running Confluence behind NGINX with SSL
- Using Apache with mod_proxy
- Running Confluence Over SSL or HTTPS
- Confluence Collaborative Editing does not work with SSL and Apache 2.4.9 or earlier
- How to check if Confluence is accessible from the internet
- Can't check base URL warning in Confluence 6.1 or later
- Collaborative Editing error in Confluence Data Center due to blocked mixed content
- Configuring Web Proxy Support for Confluence
- How to use NGINX to proxy requests for Confluence
Powered by Confluence and Scroll Viewport.