Migrating to 3CX Hosted from On-Prem Hosted VM with Custom FQDN

[DA Systems]

We are attempting to restore a backup from an existing self-hosted 3CX v20 Update 8 instance that uses a custom FQDN to a new 3CX-hosted deployment.

However, when we upload the backup file through the 3CX portal, the upload fails with an "Invalid FQDN" error.

Steps performed:

• Created a full backup of the existing 3CX PBX.
• Unlinked the existing FQDN from the 3CX portal.
• Started the process of converting the system to a hosted deployment.
• Attempted to upload the BACKUP.ZIP file during the restore process.
• Received an "Invalid FQDN" error when uploading the backup.

Could you please clarify whether the xxxxxxxb.xml file within the backup needs to be modified to include a new FQDN and license key before the restore?

If so, what should be specified for the FQDN, considering that the system will be hosted by 3CX and we understand that a new FQDN will be assigned during the hosting process?

Any guidance on the correct migration procedure would be appreciated.

 

[Evolute IT]

1. Backup without license/FQDN.
2. Shutdown machine.
3. Release FQDN in portal.
4. Click INSTALL in portal.
5. Choose "No Backup", select new FQDN, etc. Make sure ext length is the same as before.
6. Deploy the instance.
7. Upload the backup, and restore it.

For the backup storage, it's easier if you use SMB/SFTP/S3/Google as it can pull the file directly once setup in the new instance.

Follow these steps and everything will work well.

 

[Evolute IT]

Upload your backup to your new 3CX (WinSCP)

Hosted doesn't have SSH access.

Gotta use remote storage.

 

[Alphabetic]

Hosted doesn't have SSH access.

Gotta use remote storage.

"New 3CX" in this instance was referring to creating a new self-hosted but I guess what you're saying is, you can cut out this step and restore directly in to the hosted via cloud backup storage

 

[bitn2]

Me neither

@DA Systems

humour me, do this.

- Backup 3CX via CMD without FQDN and Lic
- Release FQDN
- Reinstall 3CX and use the "Install" button from 3cx customer portal to deploy to self-hosted, run through setup to generate url
- Use URL to install blank 3CX with your new FQDN
- Upload your backup to your new 3CX (WinSCP)
- Make sure 3CX up to date then restore your backup

I think you need to adjust the xml to the new fqdn. But the rest of it should work like you said.

 

[Alphabetic]

I think you need to adjust the xml to the new fqdn. But the rest of it should work like you said.

There's no XML adjustment needed.

To streamline this use cloud storage for backup.

1st backup without FQDN and Lic
Release FQDN, Deploy to Hosted and create FQDN
Link up cloud storage (copy backup to it) then restore on top

I believe this should work.

 

[bitn2]

There's no XML adjustment needed.

To streamline this use cloud storage for backup.

1st backup without FQDN and Lic
Release FQDN, Deploy to Hosted and create FQDN
Link up cloud storage (copy backup to it) then restore on top

I believe this should work.

I didnt test it but how should the backup restore without fqdn an lic?

 

[Alphabetic]

I didnt test it but how should the backup restore without fqdn an lic?

Youre running the restore from within your new 3CX and the license and fqdn isnt specified in XML so I guess it assumes whatever exists already there. I only tested it in my self-hosted installs but I had no errors when I restored this backup. It just took FQDN and lic I had specified during the fresh set up.

 

[Evolute IT]

I didnt test it but how should the backup restore without fqdn an lic?

Yes once installed