v20 migration between two VMs: public IP question

[Leo_B]

Hello,

I suspect I'm asking this for the hundredth (or maybe thousandth) time. It's simple: there's a VM running a working v20 instance, and for various reasons, I need to move this PBX to another virtual machine, which will inevitably result in a change of public IP. The question is, what's the proper way to handle this kind of IP switch? Is it enough to just make a full backup, shut down the old VM, install 3CX on the new one, and restore from the backup? Or are there some subtle, less obvious tricks involved?

Thanks in advance to everyone who responded!

 

[paulodagraca]

Hello @Leo_B ,

That is it.
Nothing more, nothing less, nothing diffrerend.

Just make a full backup, shut down the old VM, install 3CX on the new one, and restore from the backup.

Paulo

 

[SteveITS]

Note if using a 3CX FQDN the TTL for a Pro license is 6 hours. Or 5 minutes for Enterprise.

 

[KyriacosS_3CX]

Simply as another scenario, in case this is easier for you:
If the VMs are within the same environment, or of the same type at least, you might be able to move/clone/backup-restore the entire VM and have all your data - but some command line work might be needed to get the new IP set in place of the old one, and then also change it via the PBX admin pages.
Prior to such an undertaking you should disable any console restrictions though, to make sure you can access the PBX from any new LANs that might be involved.