Migrating Fisheye and Crucible database to a new server
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Summary
The purpose of this article is to outline what has to be done in Fisheye and Crucible when migrating their database to a new server and not to describe how to actually migrate the database server since the migration will differ in a number of ways depending on your DBMS, environment, and etc.
If you're looking to migrate the database server that your Fisheye and Crucible instances are connected to from server A to server B and are wondering what changes need to be made in Fisheye and Crucible to make sure they're able to connect to the database in the new server then this article is for you. However, if you're looking to migrate between databases (e.g. from PostgreSQL to Oracle 19c) then this article is not for you – please consider reading and following the steps inside the Migrating to an external database page if a DBMS change is what you're trying to achieve.
Solution
In order to ensure Fisheye and Crucible will be able to connect to the database in the new server you'll have to follow these steps:
Stop Fisheye and Crucible.
Backup your current database server.
Migrate your database to the new server using your preferred method – this is usually done using the database's own native tools.
Update the database directive inside your $FISHEYE_INST/config.xml file to make sure the connection details are still valid (e.g. jdbcurl, password, username, and etc). Here's an example of the settings you'll need to double check (and change if necessary):
1<database type="postgresql"><connection dialect="org.hibernate.dialect.PostgreSQLDialect" driver="org.postgresql.Driver" jdbcurl="jdbc:postgresql://10.158.231.21:5432/fisheye" password="mypassword" username="postgres" maxPoolSize="20" minPoolSize="5" driverSource="user"/></database>For example, if my database's address changes to 10.193.187.16 I'll need to update the jdbcurl to point to new address to ensure Fisheye and Crucible can connect to the database in the new server otherwise the application will not start up properly.
Start Fisheye and Crucible.
Was this helpful?