Relocating 3CX deployment

[MatthewHood]

Hi,
I have the need to move a 3CX deployment from a linux VM in a private cloud to another Linux VM running on a server deployed inside a clients SPN.
I've never moved a deployment in this way before including the public Static IP of the system changing.
The FQDN and license is to be kept. and reused for the new deployment.

Can someone help me out by telling me if I have this correct
The License key is bound to the FQDN so the fact they are being reused means we can take a backup of the outgoing system including the lic. key and FQDN details and restore to the new location without the need to release them?
I'm told the pubic IP of the system can simply be changed to the new static IP during the initialisation of the new 3CX instance and from there its just a matter of reprovisioning the yealink handsets?

thanks
Matt

 

[cobaltit]

Yes

 

[YiannisH_3CX]

Hello @MatthewHood

Although you can include the licence and FQDN in the backup i would recommend creating your backup without licence and FQDN and provide the licence key during the installation. This is will create a backup without network settings and will eliminate an extra step you need to perform to change the local IP of the PBX. It is up to you which method you choose to follow.

 

[MatthewHood]

Thanks Yiannis.
I have been given steps to follow which I put here for anyone else needing them
thanks.

In order to move the PBX from one facility to the other, please follow the procedure below:

1. Make a Full Backup of your current installation and make sure you DO NOT check the option "Include License Key Information & FQDN"
2. Move the Backup file to a neutral location outside the 3CX folders so it is not wiped out by the uninstall.
3. Uninstall 3CX Phone System
4. Install 3CX Phone System at the new location and in the Config Tool, select to restore a Backup and give it the Backup you made in step #1.
5. The Config Tool should ask you for a License Key, when you enter your License key, the config tool will automatically get the FQDN as well since they are already bound.
6. As you have said, then you need to reprovision the phones.

**Note:The reason for not checking the option "Include License Key Information & FQDN" is that this option also contains IP configuration, which in this case is better to be configured in the new environment during installation.