3CX migration questions

[ASTERHC]

I need to migrate our 3CX install from one VM to a new one so I can set a new password.

To try and minimise downtime as much as possible (we are 24/7, 365) I was planning to have the new VM basically setup and ready to go waiting on the restore backup screen so I can save a backup from our current instance, download the backup, shut down the VM, restore the backup to the new VM and away we go.

To get things ready I need to set a hostname and FQDN for the new VM and I cannot reuse the existing hostname as they are in use.

Will there be any issues with setting a new hostname along with new private and pubic IP address for this new VM and restoring the 3CX backup?
Will 3CX be able to accept the new hostname, FQDN, public and private IP address?

The next question I have is that when the original VM was setup Virtio was disabled. It is my understanding that disabling Virtio enables a legacy mode using an emulated IDE HDD and old Intel NIC and as such has a performance penalty.

As I am making a new VM I plan to have Virtio enabled (it is the default option from the hosting provider). Will there be any issues with restoring our backup from the Virtio disabled VM to the new Virtio enabled VM? The hosting provider uses the KVM hypervisor if that makes any difference.

 

[bitn2]

You dont need to set any hostname or anything else. Just spin up the new vm and restore the backup from the old one. Keep in mind to shut down the old before you restore the backup. If its hosted somewhere check the firewall in front of the pbx.

 

[SteveITS]

Echoing from your post elsewhere, I said:

In step 5 here choose [to] restore instead of uploading a configuration file: https://www.3cx.com/docs/manual/installing-debian-linux-pbx/#h.pa8ixc18xv5r

Note the default web server port is now 443 not 5001 so if you use the latter that will need to be changed during the installation.

The backup restores the database, any hardware changes are not related to the 3CX backup/restore.

 

[ASTERHC]

Thanks both of you. Migration went smoothly other than a very very slow upload of the backup due to hotspotting to a mobile phone.

 

[KyriacosS_3CX]

hotspotting to a mobile phone.