Restoring a backup to a new VM

[phonecheese]

Hey all,

We need to spin up a new 3CX server and wanted to verify everything before we do.

We have a new 3cx VM (Standard edition) that is currently in production in Azure. We have Azure Failover replicating to a different region. We were going to test failover and were looking into it and found that the TTL for FQDNs is 6 hours which is not good for any type of DR. So, we are planning to drop 3cx DNS and just host it in our own DNS which means:

1.taking a backup of hte server without FQDN and license
2. Dropping the FQDN in our 3cx account in the customer portal
3. Upping to the Professional Edition
4. Uninstalling the original server
5. Installing the new server
6. Applying the new license
7. Setting up the custom FQDN
8.Installing the SSL cert
9. Restoring the backup to the new install
10. Pushing out the new configs to the softphones and desk phones

Since this server is in production, I was wondering if I could adjust these steps at all if I wanted to spin up a completely new VM and leave the old one in place (to keep downtime at a minimum) until I was ready to restore the backup or at least drop the license and FQDN.

Could I just:
1.Spin up an entirely new VM with a Professional license while the old one is still in production (the new VM would be able to make calls etc at this point, so ready to go in other words)
2. get the new VM set up in our DNS and with SSL cert
3. Take a 3cx backup of the old VM (without FQDN and license)
4. Remove the license from the old VM in the Customer Service portal
5. Restore the backup to the new VM
6. Push out new configs to softphones and desk phones

Does this sound feasible?
Any other suggestions or thoughts?
Also, will 3cx with with a wildcard cert? I assume yes, but I have to ask.

Thanks!

 

[Evolute IT]

Why not use the 3CX Failover which works built-in?

Also, an Enterprise license would give you the 5min TTL on the 3CX FQDN, instead of having to manually setup the DNS and SSL.

As for your steps, yes it's doable. However, you won't be able to "push" the new config to phones and apps. They will need to be reprovisioned since the FQDN will have changed.

 

[phonecheese]

By re-provision, you just mean we would have to resend the emails and re-install the configs for softphones, correct? Then for deskphones just put in the URL to re-prov? That is what I meant, i used the wrong language though.

We would use Enterprise but we are cheap The higher ups are always trying to save money every which way they can. Also, we would rather use our own DNS as well to be honest- itis nice to have the control.

Thanks for the reply.

 

[Evolute IT]

By re-provision, you just mean we would have to resend the emails and re-install the configs for softphones, correct? Then for deskphones just put in the URL to re-prov? That is what I meant, i used the wrong language though.

We would use Enterprise but we are cheap The higher ups are always trying to save money every which way they can. Also, we would rather use our own DNS as well to be honest- itis nice to have the control.

Thanks for the reply.

You get more control but more work to manage it. The difference between Pro and Enterprise is not that much.

As for reprovision, yes, exactly what I meant.

 

[ChrisC_3CX]

Just a few notes.

Regarding reprovisioning deskphones, do bear in mind that you will have to factory reset the devices before reprovisioning IF you will be changing the provisioning method (Local, SBC, STUN).

Step 4 in your second set of steps will not be required to do(at least not immediately) unless you will be using that License Key to replace on the new server.

Also, make sure you have shutdown or uninstalled the old 3CX Instance before you restore the backup to the new.

 

[phonecheese]

Ah, thanks for that- I will add shutting down the old VM before the restoring backup step.

Also, again, there is no problem with using a wildcard/star SSL cert with 3CX?

 

[ChrisC_3CX]

Also, again, there is no problem with using a wildcard/star SSL cert with 3CX?

This should work fine yes!

 

[phonecheese]

Great, thanks!