Solved Migrate from AWS EC2 to another VM provider

[Sepultura]

Hello,

I've got 3CX running in AWS EC2 cloud. IIRC this was set up with some automatic (web?-)installer by 3CX an it uses mycompany.my3cx.de as domain. I want to migrate to another VM provider (UpCloud) because I'm already running other VMs there and furthermore they are roughly half the price.

I've installed the 3CX Debian ISO in a VM there and now I'm ready to export a backup and import it on the new VM. Should I consider anything else? As I have a my3cx.de subdomain, will the DNS settings and Let's Encrypt certificates automatically be updated after importing the backup?

Thanks!

 

[cobaltit]

Yep, it's that simple. Just make sure you shutdown the EC2 instance before installing at UpCloud so they both aren't online at the same time.

 

[Saqqara]

Backup your existing server including license key and fqdn

Shutdown the existing AWD EC2 3CX system.

On the new 3CX system, import the backup from above,

Make any changes to endpoints to point to new server if required

 

[Sepultura]

Yep, it's that simple. Just make sure you shutdown the EC2 instance before installing at UpCloud so they both aren't online at the same time.

So the running system tells the the DNS server of my3cx.de to update it's entries?
And I guess I can just start up the EC2 instance again, if the migration fails?

 

[StefanW]

Yes. When system installs or starts it will update the records. However this can take up to 10 for the TTL to export and then all DNS cache server to update. To be save plan in 30 to be sure. Also check that you have not set in 3CX a static IP.

 

[Sepultura]

It's already running on the new server. Has worked great
Another thing one should take care of are the used ports for http/https. It has suggested 5000/5001 while they have been 80/443 before.

 

[StefanW]

if you install clean to our hosting service, we will use 443.
If you have a backup which is 5001, then we will use it. Otherwise will change it to 443.

 

[Sepultura]

Hi,

I've never used the 5000/5001 ports before. I've always accessed the web interface via standard 443 port. Nevertheless during migration it has suggested 5000/5001, which I've changed back to 80/443 and my devices work without re-provision.