Upgrade to v20 methods

[desktop]

We’re currently in the process of upgrading from 3CX v18 to v20. We’ve completed one PBX so far using the "clean install + restore from backup" method, and it went fairly well. However, the official documentation seems to lean in favor of using the in-place upgrade option.

We host each PBX in a separate cloud instance. For those who have used the upgrade path, how did it go?

• Did you encounter any issues that made you wish you'd just started fresh with a new instance?
• Or did the in-place upgrade go smoothly without unexpected issues?

Our setup is fairly straightforward. No complex ring groups, queues, office hours, or holiday rules. The main user has already been converted and assigned an extension password. The only complexity is the number of extensions, but no special routing or departmental logic.

From what I understand, the two approaches are:

1. In-place Upgrade
   • Backup existing system
   • Run OS upgrade (Debian 10 → 11 or 11 → 12)
   • Upgrade 3CX to v20
2. Clean Install + Restore
   • Deploy a new instance with Debian 12 and 3CX v20
   • Restore backup from existing system

Appreciate any feedback or gotchas from those who’ve gone through either process.

 

[KyriacosS_3CX]

Hi,

I would say the restore from Backup is the fallback mechanism in case In-place is not working somehow, restore from backup might be the first choice if you want to take the upgrade as an opportunity to move to a better specked machine etc.

If they are cloud instances you can always make a snapshot/clone of the machine prior to starting the upgrade, so if something odd shows up along the way you can easily roll back, fix the issue and go again.

Best,
KS

 

[cantvchicago]

I'm in the same ocean but my boat is a little different.

I opted to abandon the Windows platform and host an on-prem Debian VM for 3cx. so it was a clean install. Everything went well but now I'm looking at two PBX instances on on my LAN and on 3cx.com. The new 3cx v20 on the new Debian VM which expires in September, and my legacy v18 which expires in Jan26

I recall 3cx was being gracious about relicensing these migrations, so I'm looking to get some clarity on that and what to do for renewal. AND my phones - these perfectly functional and well designed yaelink t46Gs... I didn't ask if they're supported. and omg if they are not....

Lastly, when I restore my backup to the clean system, what impact, if any, will that have on the functions of the running pbx?

I hope this is aligned with this thread, seems like a good part of the convo.

Thanks!

JB

 

[MayurPatel]

My canoe is floating in Azure.gov, and I’m having trouble creating a trial instance. I’m getting an authentication error. Before I update my current version 18 in Azure.gov, I need to test if the restored backup will be as close to normal as version 18. Then, I’ll take a snapshot, backup, and update.
-m

 

[MayurPatel]

Hi
I like to create a new vm with trial key v20u6. will I be able to restore my v18u9(35) backup without FQDN/key?
thanks

 

[SteveITS]

@cantvchicago Did you set up a [trial]? Buy a new license? The process is to restore your backup which moves the FQDN and license.

@MayurPatel the restore includes the key and FQDN.

 

[MayurPatel]

thanks for your quick response.. I like to restore without making new v20 live to test inbound/departments and other changes before hand.. this is 24x7 use PBX and wanted to make sure downtime will be limited to upgrade time or restore time of hour at max.
thanks

 

[bitn2]

No, you cant restore a backup without fqdn and licence. To test something you need to do it on a fresh install.

 

[MayurPatel]

need to see my own data on update before going live.. thanks for that info..

 

[bitn2]

That wont work as long as your "old" pbx is online.

 

[MayurPatel]

that is reason for creating vm with trial key and restore of backup.. I guess will have to do blind update and take chance.

 

[bitn2]

Is this your first pbx to upgrade to v20? When you check all the stuff before upgrade there will be no problem at all...

 

[KyriacosS_3CX]

that is reason for creating vm with trial key and restore of backup.. I guess will have to do blind update and take chance.

Take a snapshot of the VM before the upgrade, preferably while shut down if possible, then you have a very quick roll-back. But if the upgrade steps are followed you should not expect any issues.

 

[Alphabetic]

Sometimes maybe good, sometimes maybe... We couldnt do inplace upgrade as the hardware wasnt there otherwise I would have. Inplace is quicker. However, my predecessor installed the 3CX via CLI which gave me the opportunity to install it with the ISO so it was a win win for me. Plus, the backup, reinstall and restore allowed me to drop the 5001 management port.