Move 3cx backup from Windows server2016 to 2019

[chrishoobly]

Good day everyone
We are planning a simple enough exercise of installing the v18 3cx software onto a brand new Windows 2019 server (VM), exporting the config from old 2016 server and importing it into the newer version server (would have attempted 2022 but I haven't seen that it is officially supported yet?).

The new server is going to have the same internal ip address to make things easy and I was planning on naming the server the same name - and this is my question

Lets say my current 3cx server is called 'ServerA' and is in Active Directory connected to the domain ( so serverA.domainname.co.uk) and has ip address of 192.168.10.50.
I cannot create my new server in advance to be called 'ServerA' as it already exists - correct? I need to name it something else for the time being.

Do I have to have my new 3cx server named exactly the same as the previous one or can I name this one say 'ServerB' and simply switch off the old server, move the ip address to ServerB and the imported backup would work?

Or, if it is linked to the AD name, am i going to have to rename the current ServerA to ServerA-old before editing ServerB to ServerA for this to work

I have read alot of discussions in here which don't discuss any AD edits or changes - most say shut off the old server, fire up the new one and import the backup and state that if the ip address is the same it will worK.

My concern is if i rename the current one, register a new server wiht the old name in AD and the migration didn't go as planned, I would be trouble if we reverted and we couldnlt get the old system running once again

Thats a bit rambly, I apologise but hopefully you understand my concerns about the server name. I donlt know if the system relies on the exact server name in AD or not

Thanks to anyone reading and I appreciate any advice - we donlt have any official support which is why it is a worry for us
Thanks again

 

[Saqqara]

Any reason why the 3CX server is connected to the active directory - all our machines are in a workgroup. 3CX does not interact with AD

If you need to machine to be connected to the AD, just give it another name - 3CX does use the server name for connections - just the IP address or the FQDN name internally.


To migrate to new server

1. Backup with FQDN , License , Voicemail and Recordings. Move the backup file to local PC

2. Switch off the old machine.

3. Change IP address of new machine to old server IP

4. Install 3CX using restore from backup option.

 

[chrishoobly]

Thanks Saqqara - thats the information that has just made my friday night work much less stressful
Very much appreciated

 

[VasilisV_3CX]

Hi @chrishoobly,

Let me know if you face any difficultly along the way.

 

[chrishoobly]

Thanks Vasilis - very kind of you

I do have another quick query as part of the v18 migration if someone can answer for us - we currently use the 3cx softphone - does this continue to work, but just upgrades itself to a newer version when they open it, or do our users need a new interface?

 

[VasilisV_3CX]

Hi @chrishoobly,

When you upgrade to v18 they can continue to use the Web Client (Softphone) and will be given an option to install the new Desktop App (a non-browser based softphone). You can also continue to use the v16 Windows Client and will be able to use the mobile clients as well.

 

[chrishoobly]

Hi @chrishoobly,

When you upgrade to v18 they can continue to use the Web Client (Softphone) and will be given an option to install the new Desktop App (a non-browser based softphone). You can also continue to use the v16 Windows Client and will be able to use the mobile clients as well.

Wonderful - sounds easier than I expected. Many thanks for all the replies

 

[VasilisV_3CX]

No problem @chrishoobly, let me know how it goes and feel free to ask if you require any further assistance or info.