Upgrade from v15.5 to v16

[Alltask_Ltd]

Hi Everyone,

Got a question regarding the upgrade of our system. Currently running v15.5 on Windows Server 2012 R2 Std and want to perform the upgrade to v16, but notice that Server 2012 R2 Std isn't on the supported platforms list. Will I need to migrate the PBX to a new server running 2016, or will it be OK to do an in-line upgrade? I'm just looking for the most simple upgrade path here. Have also considered moving across to Debian 9 if it is the case that it won't work on Server 2012 R2. What would everyone recommend?

Thanks in advance.

 

[Saqqara]

Server 2012 R2 is not supported any more - https://www.3cx.com/docs/manual/

I would not do an in place upgrade of the operating system - would always start from scratch.

As for what you should go for, what are you conformable supporting

 

[JohnS_3CX]

Hi,

You have a couple of options I can suggest:

1.) Take a full backup of the 15.5 (must be on SP6) and restore the backup on a fresh prepared server with Windows Server 2016 or 2019.

2.) Take a full backup as above. Keep the 2012 R2 Server, but install Hyper-V to deploy a Debian Version of 3CX using your backup.

3.) Take a full backup as above. Wipe the existing Windows Server 2012R2 and deploy our Debian ISO on it Directly.

Either way, you need to ensure that the PBX ends up running on a Supported OS so choose which OS better suits your needs and decide accordingly.

If you have any questions before you proceed, please don't hesitate to ask

 

[Alltask_Ltd]

Thanks for all the replies. What is the 15.5 version number for SP6, as I am unsure if I have that installed already.

We have the current Server with 3CX running on a Hyper-V setup, so deploying a new image isn't an issue. My only concern with the 3CX on Debian was supporting the OS, as it isn't as familiar - but linux builds are fairly stable these days.

Would I be able to build a new server, and restore to it while the current 15.5 server is still running without causing any issues with licencing or anything else? I could always put it on a staging network I guess..

 

[Saqqara]

You can not have two 3CX running the same license key, it will cause all sorts of issues and will probably take down your existing working 3CX

Installed 3CX from the 3CX image takes minutes, the longest part will be restoring your existing config

How big are you backups ?

 

[JohnS_3CX]

Hi,

It should appear with this version number in the MC. Make sure you have this version as a minimum.


Once you install the new version, the key will be upgraded to V16 so there is no going back after that.

You cannot run them in parallel, this will cause issues with your FQDN, and the registration of all phones and clients. One machine needs to be shut down entirely, while you setup the new one. You can move the IP to the new one too, so all your existing devices and port forwards point to the new machine.

There is a helpful guide for upgrading, which should answer quite a few questions, but we will be happy to address any other concerns you may have after reading this https://www.3cx.com/docs/upgrading-pbx-v16/

 

[Alltask_Ltd]

You can not have two 3CX running the same license key, it will cause all sorts of issues and will probably take down your existing working 3CX

Installed 3CX from the 3CX image takes minutes, the longest part will be restoring your existing config

How big are you backups ?

OK, won't do that then..

Backups are 580MB in size currently.

 

[Alltask_Ltd]

Hi,

It should appear with this version number in the MC. Make sure you have this version as a minimum.
View attachment 16178

Once you install the new version, the key will be upgraded to V16 so there is no going back after that.

You cannot run them in parallel, this will cause issues with your FQDN, and the registration of all phones and clients. One machine needs to be shut down entirely, while you setup the new one. You can move the IP to the new one too, so all your existing devices and port forwards point to the new machine.

There is a helpful guide for upgrading, which should answer quite a few questions, but we will be happy to address any other concerns you may have after reading this https://www.3cx.com/docs/upgrading-pbx-v16/

OK, understood. I will build a fresh server, and then shut the old one down before I perform the upgrade on the new one.