Moving from Windows to Debian

[mixig]

Hi,

currently 3CX v15.5 is installed on Windows server.
Now we are moving 3cx to Debian.
When creating a backup on Window server do I need to select "Include License Key Information & FQDN or not" in backup menu? If selected, then during restore licence will be also restored?
If no, i will put licence during the new instalation/restore procedure?
FQDN and public IP will be the same

Thanks

 

[jimbo59]

Make both backups but you will use the one with license and FQDN.

 

[eddv123]

You can backup a windows installation and restore to a linux installation without issues. During installation your Public IP, Licence and if using a 3CX Supported FQDN and certificate are bound together.

Unless any of these are changing simply migrate the full backup. Also consider Full cone NAT from public to private IP if your local 3CX IP of the server is changing.

 

[mixig]

OK, thanks

 

[YiannisH_3CX]

When creating a backup on Window server do I need to select "Include License Key Information & FQDN or not" in backup menu?

I would recommend NOT including the licence and FQDN info when creating a backup for moving the PBX to a different machine, especially if the local IP of the server will change. Upon restore specify the licence key and the FQDN will be automatically be selected as it bound to the FQDN.

 

[Silly English Kniggit]

I would recommend installing SP2 on the target server before restoring.

 

[NickD_3CX]

The safest way to ensure nothing goes wrong is to:

• Backup without option "Include License Key Information & FQDN"
• Bring Windows (old) server offline
• Install V15.5 on the Debian (new) server
• During the installation wizard, load the backup file you made
• Continue with the Wizard filling in all information as necessary.

This is the textbook way.

Now if you plan on creating the Debian VM using the 3CX PBX Express Wizard, because the wizard itself currently does not allow you to use a backup, then you would have to go the way @Silly English Kniggit pointed out, but I wouldn't prefer it in other cases.

 

[stever]

If you do your daily backup with license and FQDN and the machine crashes, can't you restore to a new machine assuming that it has the same IP address? Is so, are there other reasons to not backup the license and FQDN if your recovery plan would utilize a PC with the same IP?

 

[NickD_3CX]

If you do your daily backup with license and FQDN and the machine crashes, can't you restore to a new machine assuming that it has the same IP address? Is so, are there other reasons to not backup the license and FQDN if your recovery plan would utilize a PC with the same IP?

Of course, that is the point of this option, to make restoring a backup easier, but as you said, assuming that the system to which you will restoring will have the same FQDN and License Key.

Making backups without this option just gives you a bit more flexibility when restoring, e.g. if you want to use a different license key and/or FQDN. If you want to do this and your backup has the License Key and FQDN information in it, the proper way would be to install with the License Key and FQDN that the backup has, then make a new backup without them, then uninstall, then re-install using the new backup.