Solved Moving a 3CX instance from Azure to Azure (different tenancy)

[Martyn Barlow]

What would be the process for moving a 3CX instance currently running happily in Azure within one tenancy to Azure running in a completely different tenancy?

I get that I need to take a backup but unsure if I include the FQDN in with that and then where I go from there. I have searched the forums but not finding anything conclusive.

Any pointers would be hugely appreciated. Thanks in advance.

 

[Evolute IT]

Backup WITH everything checked, download that.

Scrap the instance and use PBXExpress to deploy a new one in the new tenant, restore the backup there.

 

[StavrosA_3CX]

Hello Martyn,

I just want to add to what Frederick said,

It depends what you are trying to do:

a) if you are going to create a new account in Azure using the same License Key and FQDN, then:
1) You need to take a backup of the current PBX without excluding anything. FQDN & License Key included.
2) You will need to generate another Azure Tenant ID.
3) Then you need to stop the current machine.
4) Login to your portal and Reinstall the same Key, if your backup is up to 1G then you can restore it there. If not then you will have to restore it post installation.
Done - You will have the same LK and FQDN in another Azure tenant.

b) if you are going to use a different License Key:
1) Create a backup but this time exclude License Key and FQDN.
2) You will need to generate another Azure Tenant ID.
3) Then you need to uninstall and release the FQDN from the current installation.
4) Install the PBX from scratch and restore from backup. Done - You will have the different LK the same FQDN in another Azure tenant.


c) if you are going to use a different FQDN same License Key:
1) Create a backup but this time exclude License Key and FQDN.
2) You will need to generate another Azure Tenant ID.
3) Then you need to uninstall and release the FQDN from the current installation.
4) Select a new FQDN.
5) Install the PBX from scratch and restore from backup. Done - You will have the same LK different FQDN in another Azure tenant.

 

[Martyn Barlow]

Thank you both for your replies.

@StavrosA_3CX - I've run through scenario a which does apply to me (using the new portal layout) however when I provide it with the backup file it come back stating "Backup FQDN [FQDN]. is different to License Key FQDN" and I cannot proceed.

Any ideas?

 

[Martyn Barlow]

The other question I have is can you safely use this method to move from v16 to v18?

 

[AlexisV_3CX]

Can you verify that the backup does include the License key and FQDN and that you are not trying to restore it to a different Subscription ?

Regarding your question, the safest way to upgrade from v16 to v18 is from the Management Console by navigating to the 'Updates' button at the top-right section of the page.

 

[NikosT_3CX]

@Martyn Barlow can you please try now and provide me a feedback ?
Thank you !!