Migrate from Azure to Vultr with v18

[3ChrisX]

Hi

We have a current "on-premise" 3cx instance in Azure and we're looking to migrate to "self-hosted" Vultr. The following describes most of the important info for consideration.

• xxxx.3cx.co.uk domain is used and needs to move over
• the new Vultr instance is installed from the marketplace ready to restore the backup
• a backup of the instance in Azure is completed, including all available content types
• phones connect via a combination of SBC and direct SIP / STUN (Fanvil x5u) depending on location
• the SIP provider is Gamma

The parts I believe I understand so far are:

• Restoration from backup during initial set up of the Vultr instance
• The change to the SIP provider

The questions I have are:

1. How do I link the new instance to 3cx portal after restoration?
2. Can I provision the existing domain on the new instance?
3. If the above is possible, will the SBC and existing phones just swap over to the new instance once the domain is moved and propagated?
4. Are there any other considerations before I start the process?

Thanks in advance.

 

[Evolute IT]

1. With the backup, FQDN & license are included. You don't have to do anything, it will be brought over.

2. See 1.

3. Yes, after a little while since DNS need to update. If you use a custom FQDN, you'll need to manually change the IP in your DNS.

4. Check your v18 version. If it ends in .23, you won't be able to restore the backup directly on Vultr, since the Marketplace image is v18 but ends in .20 (there was a small hotfix since.) So, if you try to restore it, it wouldn't work. You'd need to mess around with the backup and update process.

 

[3ChrisX]

Thanks for the swift reply and detailed info.

1. This makes sense. Follow on question, what is the cutover process? If I restore first, then work on other things, at what point will the old system stop working / be unlinked from 3cx portal?
2. Lovely!
3. Understood.
4. I'm on the version ending .20 still. I disabled auto-update to prevent v20 getting installed, as we use some features that aren't supported. Sounds like I've had a lucky escape on the hotfix release, then.

 

[Evolute IT]

1. Backup, download the backup, spin up the Vultr VM, wait for the setup wizard to be ready, then shutdown the Azure VM. After restore, the license and DNS will be updated for the new instance. Make sure you use the same HTTP/HTTPS ports during setup than what you had on Azure, otherwise phones and SBCs will have a bad time.

4. Yeah you're lucky. You will be able to just restore the backup without messing around too much.

 

[3ChrisX]

The sequence of shutting down the existing instance was that part I was unsure of.

Cheers for clarifying.