What is the recommended way to move Stash/BitBucket Server

Deleted user November 1, 2016

Were currently running Stash 3.11.2 on Windows Server 2012 DB on MS SQL Server 2012 and want to

migrate to Bitbucket Server 4.10 on Linux with Postgress SQL as DB.

What is the recommended migration path for this?

Straight forward I'd think:

Setting up an empty instance Bitbucket Server 4.10  on Linux

Shutting down the Windows Instance.

Copying the content of the Home directory to the Home directory of the new instance

Starting up the Windows Instance.

Running the DB Migration Wizard to move the contents of MS SQL to Postgress SQL

Shutting down the Windows Instance

Starting Up the Linux Instance.

 

Or must we have 3.11.2 also on Linux to do that?

 

2nd:

How can we prevent users pushing to the Windows Instance while the Migration Wizard is working?

 

Thanks for your advice

Harald Mueller

3 answers

0 votes
Deleted user November 3, 2016

We have now tried the move from Stash 3.11.2 to Bitbucket Server 4.10

For Backup we used client 1.9.1 on Windows and for Restore we used client 3.3.0

The restore attempt returns following error message:

[gitadmin@daegit01: ~/bitbucket-backup-client-3.3.0]$ java -jar bitbucket-restore-client.jar /home/gitadmin/stash/stash-20161103-131215-037.tar
2016-11-03 13:54:42,455 INFO         Initializing
2016-11-03 13:54:43,386 INFO         Unpacking stash-20161103-131215-037.tar to /opt/atlassian/application-data/bitbucket
2016-11-03 13:54:43,708 ERROR        stash-20161103-131215-037.tar could not be restored
com.atlassian.bitbucket.internal.backup.client.RestoreException: This version of the Restore Client may not be able to restore backups created by your version of Stash due to the following critical issue(s):
BSERV-8280: Restored database tables may be generated with an incorrect column type.
All versions prior to 4.0.0 are affected by this issue. See http://jira.atlassian.com/browse/BSERV-8280 for more details.
Please switch to a version compatible with Stash 3.11.2
        at com.atlassian.bitbucket.internal.backup.client.DefaultBlacklistService.validateRestore(DefaultBlacklistService.groovy:59) ~[bitbucket-backup-core-3.3.0.jar:3.3.0]
        at com.atlassian.bitbucket.internal.backup.client.DefaultRestoreClient.restore(DefaultRestoreClient.groovy:75) ~[bitbucket-restore-client.jar:3.3.0]
        ... 4 more frames available in the log file

 

What should we do now?

 

Regards

Harald

 

ThiagoBomfim
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 3, 2016

Hi Herald,

Please try to backup and restore with the same client release 1.9.1. Use the same client to restore. Once you restored it, you can point a newly downloaded installation to that home directory and all should work.

0 votes
Deleted user November 1, 2016

Wow, that was fast. We'll try that.

Thanks

Harald

 

0 votes
ThiagoBomfim
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 1, 2016

Hi Herald,

The backup client is the best approach:

Hopefully that will help you move forward.

Best regards,
Thiago Bomfim
DevTools

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events