Migration From windows to Linux

vivuu November 28, 2017

Now Our Prod setup (Jira- 7.1.9, Bitbucket-4.9.1, Confluence-5.10.0, Crowd-2.11.1 in Windows server and it should be migrated to linux machine in another domain with a different url .


currently in windows the atlassin application are running behind reverse proxy and for authentication we are using crowd internal directory ?

So please let us know what are the steps need to be implemented for data migration to new instance in the linux (windows to linux )

 

using MSSQl DB in both environment

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 28, 2017

Are you changing the database at all?

If not, then the easiest route for all the applications is

  • Install an identical version of the application on the new machine
  • Get each one working with an empty MS-SQL database, just so you know they work before the data goes in
  • Change the proxy settings to point to the new server
  • Take a backup of each of their database connection files, just in case (dbconfig.xml in Jira home for example).  Or backup the whole lot!
  • Stop the application and copy the home directories from production over to the new machine.  Be careful to check ownership and permission on the copies - they must be owned by, and accessible to, the user who is going to run them
  • Restart the instances. 

The copy of the home directory should mean that the pointer to the old production database is carried over, so the new boxes should simply take over from the old ones.

vivuu November 28, 2017

Thanks Nic.

 

So what about new domain name change and reverse proxy

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 28, 2017

Sorry, missed the domain thing.

You'll need to change both sides of the proxy.  A proxy says "When users land on this part of a site, serve up content from those servers over there".  I assumed, wrongly, that it was only the Atlassian servers moving, so you'd only have to change the proxy to point at "those servers over there".   If the domain is changing, you'll need to change the other side to represent the new domain, and also the base urls in your Atlassian services to match the new location.

Suggest an answer

Log in or Sign up to answer