Solved

Upgrade 5.2 on Windows Server 2012 R2 to 5.3 on Windows Server 2016 or 2019


Hi,

we run K2 5.2 on Windows Server 2012 R2 ...

For the latest Version 5.3 (or ine of the next releases) we have to upgrade the Windows Server Version as well.

But just upgrading Windows 2012 to 2016 is no option for us. That means, we are going to setup a new Windows Server 2016 or 2019. But that means again, that we will have a clean server without a K2-Installation at first.

What is the best way to migrate the K2-Solutions  to the new Server?

Andi

icon

Best answer by JacquesP 28 May 2019, 09:01

Good day AndreasG

 

I have attached documentation below that explain your situation and the steps to be followed. The first documentation is an official K2 document explaining the process. You may just choose the relevant scenario and follow the steps. The second document is a community post where the same steps are explained that exists in the first document.

 

Note: It is always advisable to make backups before such changes are made.

 

Documentation:

1. https://help.k2.com/kb001356

2. https://community.k2.com/t5/K2-blackpearl-Articles/How-to-move-existing-K2-installation-and-database-to-a-new/ta-p/94036

 

If this reply solved your problem or lead to the solution please remember to mark it as a Kudo or Solution. This will show other users that this response is the answer to their question and they can just follow the solution accordingly.

 

Best Regards

Jacques

 

[K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

View original

5 replies

Good day AndreasG

 

I have attached documentation below that explain your situation and the steps to be followed. The first documentation is an official K2 document explaining the process. You may just choose the relevant scenario and follow the steps. The second document is a community post where the same steps are explained that exists in the first document.

 

Note: It is always advisable to make backups before such changes are made.

 

Documentation:

1. https://help.k2.com/kb001356

2. https://community.k2.com/t5/K2-blackpearl-Articles/How-to-move-existing-K2-installation-and-database-to-a-new/ta-p/94036

 

If this reply solved your problem or lead to the solution please remember to mark it as a Kudo or Solution. This will show other users that this response is the answer to their question and they can just follow the solution accordingly.

 

Best Regards

Jacques

 

[K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

Hello  @AndreasG,

 

To add on what @JacquesP said you have to move over the current database to the new server.
This will ensure that the data integrity of the K2 database is kept, and prevents any complications due to improper selective data migration.

 

Regards,
Beswick

 

[K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

Has anyone done an in-place OS upgrade from 2012R2 to 2016 with 4.7/K2 Five installed?

Would like to hear about your experiences.

Hi Pyao

 

1. This is what happen when you try to upgrade without removing installed programmes, it seems like it is not advisable to do in-place OS upgrade only clean installation is recomended according to the screenshot below

 

 

Should you find the information from the article useful or leading you to the answer please mark as "Solution and/or Kudo", as it will assist other k2 developers with relevant information in the near future.

 

Best Regards

Elvis

 

[K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

That example is if you try and upgrade a Domain Controller. No sane IT Sys Admin would ever do that. Inplace upgrades of other server roles are viable, infact K2's blog has an example of their inplace upgrade of 2012R2 to 2016 for with K2 installed. 

I'd still be hesitant to do it on a Production Server mind you, but thats me ;) 

Reply