Bitbucket 4.13 migration to Bitbucket 5.13 from Windows 2008 server to Windows 2016 server

[Ramana Rainn]

We are currently have Bitbucket server 4.13.0 version on Windows 2008 server. We plan to install latest version 5.13 on Windows 2016 server.

The approach is to install 5.13 on Windows 2016 server and create new empty SQL database while installation. For testing the new version, I plan tcopy the home directories from old server to new server and restore the new SQL database from production SQL database backup. Do you see any issue with this approach for testing?.

Once testing is successful, I'm thinking about below two approaches to go live for new version on new server.

Could you please advise one which one is best approach and the pro's and con's about these two.

Approach 1:

      - Stop the Bitbucket instance on old and new servers

      - Sync the home directory data between old and new servers

      - Restore the new database from current production database backup

      - Start the Bitbucket instance on new server

      - Test the application

Approach 2:

       -  Stop the Bitbucket instance on old server and new server

      -  Update the bitbbucket.properties on new server to use current production database name and database server 

     -  Sync the home directory data between old and new server

     - Start the Bitbucket instance on new server

     - Test the application 

[Yogesh Mude]

HI @Ramana Rainn

If you see there is no dependency about the bitbucket upgrade like other tools (Jira, confluence), you can upgrade your bitbucket v4.13 to latest.

I will suggest as below.

First took the whole backup(Installation, Home, and database) of old bitbucket server.

1. Make sure Java JDK and git are installed on the new server.
2. Stop Bitbucket server on the Old server.
3. Take the Backup of Bitbucket Home directory ($BITBUCKET_HOME).
4. Copy $BITBUCKET_HOME from the old server to the new server.
5. Run the same version of Bitbucket server installer and select the Upgrade path. All of the default values should be correct.
6. select an empty directory for the Installation path.
7. Choose the copied $BITBUCKET_HOME path for the Home directory.
8. Uncheck Launch bitbucket server automatically.
9. Start Bitbucket server and Elastic bitbucket server from Windows services.

Please let me know your thoughts on this.

[Ramana Rainn]

Thanks Yogesh for your reply. We have only one environment so I will have to test the new version with different database before we go live on new server. Not sure your approach applies to my case. 

Do you see any issue by installing the latest version with empty database ? and the later restore the database and copy the home directories or point it to current database during cut-over.