migrate cloud "jira server" and "jira confluence" to self-hosted environment question

[new jira user]

Hi,

we already have a self-host "Jira servicedesk" (server license) running on linux - but now would like to migrate existing cloud "Jira server" (project tracking) and cloud "jira confluence" (wiki) - instances to also be self-hosted - and also take advantage of "integration features" (between servicedesk and server/core )

but am very confused on what this is supposed to look like?

is it (scenario #1): 

download 2 trial-eval-packages (jira-server, and jira-confluence), run each install scripts, point each to the same mysql database server, but each will have its own database. Then in cloud portals, backup both cloud apps to zip files, then import each zip into each via its own backup/restore web console link. Now with 3 "servers" - try 'application linking' between them? (applications => application links ) - This seems to be how to "integrate" self-hosted servicedesk with cloud jira server?

or is it (scenario #2):

based on this doc link => https://confluence.atlassian.com/adminjiraserver/installing-additional-applications-and-version-updates-938846848.html

from the already running self-hosted "jira servicedesk" web console - go to "applications" => "versions & licenses" => look on the right side for "jira software try for free" (very hard to notice this since it looks like a spam ad or something?) - and then somehow that button does magic install(?) - in other words, if u don't do it this way - then "integration" features might not work? maybe this installs "jira server" into the same database instance/schema as jira servicedesk?

Maybe is this how self-hosted jira servicedesk + jira server (project tracking) + jira confluence is done with a "server license" ( versus data-center which is more expensive license ) and with "integration features" as often described?

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

There is no "jira confluence".  Jira and Confluence are two independent (but often linked) systems.

It is going to be easier to treat them as such.  Let's look at Confluence first:

1. Download and install the latest version of Confluence
2. Run it, configure the minimum, but do not put any data into it, just get it ready to use
3. Get a backup of your Cloud Confluence system
4. Import that backup into your new Server install

You can do the same for Jira, but there are extra layers - you might have Jira Software and/or Jira Service Desk installed on top. 

• If you have one of them, then do not do the move with a Jira Core install, but use the installer that matches (i.e. if you have Service Desk, install Jira Service Desk Server)
• If you have both, then download and install Jira Software and when it is ready to start using, go to Admin -> manage applications and add Jira Service Desk

Then do the import from the Cloud Jira backup

However.  You have an additional step.  You say you already have a Jira Service Desk Server running.  The process above gives you a new server, it is not a merge.

You should still do the "empty install and download and load Cloud into it", as that gives you a Server installation from which you can merge the data into the main server (you can't merge directly from a Cloud download, I've never seen any merge work without this step)

[new jira user]

Hi Nic,

this is very helpful - but still a little confused on things - maybe if i'm on same page:

0) jira "confluence" - ok - is separate - ok - very straightforward cloud => self-hosted steps. setup new machine/server, install confluence, take cloud confluence backup, restore onto new self-hosted install => boom => done ;) - ok that seems to be clear ;)

we have "Jira servicedesk" self-hosted - "server" license ( vs data center license - so we're only installed on 1 physical server )

we have "Jira server" cloud (project tracking thing) - want to "migrate" to self-hosted 

i would guess this is similar how self-hosted "jira service desk" is done - download the .bin file from jira, install it on new server.

but now some extra complications seem to block this path:

1) cloud backup file (zip) doesn't easily install onto new self-hosted "jira server" install?

2) "licensing" issues that maybe restrict how "Jira server" is installed (???)

From your above notes:

1) i should download "jira servicedesk" bin file and do fresh install into new server - no data - just software installed

2) "install" "jira server" not via the download bin file method, but instead via web-console in new "jira servicedesk" - and via add plugins or application version/licensing link - find the button that does "install jira server"...

again - the reason for doing it this way appears to be:

a) licensing restrictions? depending on purchased license?

b) integration features? if u don't do it this way - then integration between existing jira-servicedesk and new jira-server won't work right/100% ?

c) cloud backup => self-hosted restore isn't straightforward?

but back to list of steps...

3) do import of cloud backup from within web-console in above step#2 

note: restore from backup seems to say warning will lose data - but i guess that is why your saying to do fresh install of "jira servicedesk" - there's no risk of losing any data ;)

4) and then the last step(s) involve "merge" - i don't quite understand "merge" purpose? but will google, and keep digging...

sorry if this is a bit long - but to recap - there appears to be 2 "paths" for installing self-hosted "jira server"

1) path1 = standalone on new machine, download .bin file, do the new install. Then jumping through hoops to get cloud-backup of jira server into this new install. (in a nuthsell?)

2) path2 = from within an existing self-hosted jira-servicedesk, "install" new "jira server" (via plugins or the versions/licenses link under system - a button to install 'jira software' ) => this appears to be "jira within jira?"  install - maybe there's some licensing reason for this? whatever - but this looks like another path to installation of "Jira server" self-hosted?

I think your helpful comments above are for path1 - and will try this as well - however, it now sounds like we might have to explore path2 (due to licenses??) - in which case i will try to refer to your above notes as well - thanks again for helpful info! Very much appreciated!

[Nic Brough -Adaptavist-]

No, I'm afraid you are jumping around all over the place, and you're saying things that make no sense.  For example "we have "Jira server" cloud (project tracking thing) " - Jira is either cloud or server, it can't be both.

I am very unclear on what you are trying to do or what you expect to end up with.  So I will try to explain an example that I am currently involved in working through.

Current situation, three teams have separate installs:

• Jira Software on Cloud
• Jira Service Desk on Server
• Jira Software on Server

End goal

• One single Jira instance on new hardware

The process to do this:

• Pick the Jira that would be the most painful to try to merge into another Jira.  In this case, it's the Jira Software on Server
• Create the new service instance by running the installer for Jira Software
• Add Jira Service Desk to it
• Migrate Jira Software from Server on to it
• Merge Jira Service Desk instance into it
• Merge Jira Software from Cloud into it

The important point here is the "merge" - you can't just import a backup into a system to merge two together.  The import of a backup overwrites the target system, it is not a merge.  You can move a single system from one place to another reasonably easily, but that is totally different to trying to get a two systems into one place.

Given that example, could you tell us what you currently have and where you're trying to get to? 

[new jira user]

Hi Nic,

Thanks for the helpful info & detailed replies - this is very helpful!

Sorry - you're right - i'm mistakenly saying "jira server (cloud)" when i should be saying "jira software (cloud)" ;) 

what we have:

• jira servicedesk self-hosted server-licensed
• jira software cloud
• confluence cloud

what we're trying to do:

• keep jira servicedesk self-hosted server-licensed
• self-host both jira software and confluence
• enable "integration" between the 3 products ( "seamless linking", etc)

there appears to be 2 install options for self-hosted that are confusing:

1.  separate installation => for each product. download .bin file from jira, install into its own server, directories/folders, files, and running process(es), and its own database
2. jira-within-jira installation => looks like from within jira servicedesk webconsole - under system - applications - versions/licensing - 'add jira software - try for free' link/button - seems to piggy-back? the jira software onto/into the jira servicedesk install - same processes, tcp ports, folders, files, processes, and database?? mixed in somehow?? 

in your above reply "the process to do this" - you mentioned that after installing fresh jira software install - "add jira service desk to it" - some questions spring to mind:

• is that via option#2 install (jira-within-jira) system - apps - version/license link?
• Does "seamless integration" between jira software and jira servicedesk only occur when installed this way? 
• Does a license restrict/constrain one to do an install like this? versus option#1 install - separation style. In other words, option#1 is maybe only available via a different license?

after installation is sorted - the next steps if i'm understanding - appears to be a two-step where:

1. cloud-backup is restored into freshly installed jira (self-hosted)
2. "merge" process is done - it seems when multiple instances of same jira product need to become 1? after some googling - it seems this is best done via a plugin - some posts mention 'project configurator' as making this process very easy/smooth sailing
   
   

i'm wondering if in our case - if we maybe can skip the merge?

• since we only have 1 jira software instance (hosted in cloud) - maybe we don't need to merge anything?
• we would install jira software (option#1 separate style if all things equal) and then attempt cloud backup restore into it - no problem if it wipes/overwrites data - since it's a new self-hosted install?
• same thing for confluence
• somehow enable "integration" between these 2 new separate installs - and the existing already running jira servicedesk - there's 'application linking' link from system - applications - application linking link ?

But am confused by a few things:

• are we constrained (either license constrained or integration feature constrained) to install via option#2 (jira-within-jira)?
• thus - restore from cloud backup won't work - as it will wipe out jira servicedesk self-hosted server-licensed current data? And thus - a merge option is needed?

really appreciate any feedback on this - many confusing points to this process...