Upgrading from v18 to v20 on Windows server

[JohanFer]

Hi
I have upgraded all my debian instances to v20.

I now have 2 enterprise customers with on prem 3cx on v18 update 9 build 31, both running on windows server 2016. Hosted in a data center with fortinet firewalls and sd-wan to 30 remote site with almost 2000 extensions. The system is very healthy on v18.
HA activated with standby server
Teams integrated

I just need some peace of mind to know that the upgrade to v20 will be hassle free.

I know I must take a full backup, uninstall v18 and install v20 and restore my backup.

Is there anything I need to be on the lookout for?

Any info will be appreciated.

Regards
Johan

 

[bitn2]

There is a lot of stuff you have to look for. Did you checked the upgrade path? But there more things to check.

 

[JohanFer]

I believe v20 for windows is only available in update 2 beta?
Is it safe to upgrade or wait for another release update?

 

[bitn2]

Its U3 Final already. But this it not what i mentioned in my post. Did you checked the upgrade path for v20. This is the first thing you need to do. After that there are more things you could check to avoid any problems after upgrade.

 

[JohanFer]

Only what I read here.
https://www.3cx.com/docs/manual/phone-system-installation-windows/

 

[bitn2]

Have a look here: https://www.3cx.com/docs/upgrading-pbx/

Also check your IVRs because DTMF isnt avaiable anymore and your trunks. If you have an unsupported trunk, check your template because it could be possible that it isnt avaiable on v20.

 

[VoIPTools]

For a customer this big, if you have the infrastructure to do so, I would keep the original server intact and perform the upgrade on a 2nd server/VM. That way, if anything goes south you can quickly revert back to the original server. Just ensure the original server is turned off while you perform the new install.

 

[bitn2]

For a customer this big, if you have the infrastructure to do so, I would keep the original server intact and perform the upgrade on a 2nd server/VM. That way, if anything goes south you can quickly revert back to the original server. Just ensure the original server is turned off while you perform the new install.

A snapshot would do the same. Another good idea is to switch to linux.

 

[VoIPTools]

It's all about risk. I don't recall ever having a snapshot get corrupted or fail in some way, but you never know. Again, if you have the infrastructure, in my view, spinning up a new VM and installing a clean instance of Windows is the safest/cleanest approach. But I do agree, if you have Linux expertise, I would move to Linux too.

 

[JohanFer]

A snapshot would do the same. Another good idea is to switch to linux.

I would have liked to move to linux but the customer wants to keep it windows.

 

[baspesfasf]

I have a question regarding departments. I read this in the url https://www.3cx.com/docs/upgrading-pbx/

1. Move your Queues, IVR & Ring Groups to the correct department

In V18 there are no departments. What happens when I import in V20 a backup of V18 (with the did's/queues etc)? Where can I find the queues I made? Do I move them from one place to another? Can I prepare some things before upgrading?

 

[JohanFer]

I have a question regarding departments. I read this in the url https://www.3cx.com/docs/upgrading-pbx/

1. Move your Queues, IVR & Ring Groups to the correct department

In V18 there are no departments. What happens when I import in V20 a backup of V18 (with the did's/queues etc)? Where can I find the queues I made? Do I move them from one place to another? Can I prepare some things before upgrading?

The queues in v20 is under "call Handling"
They were imported from my v18 to v20 when I upgraded my debian systems.
Not sure if it will work the same for Windows

 

[NicholasP_3CX]

The queues in v20 is under "call Handling"
They were imported from my v18 to v20 when I upgraded my debian systems.
Not sure if it will work the same for Windows

The only difference is the operating system.

There is no configuration difference between Linux and Windows 3CX. Just the operating system it sits on.