Restoring backups to another server- extension data for provisioning

[phonecheese]

Hi all,

So i am migrating all the extensions and stuff frmo the old server to a new server. I am doing some prep ahead of time including exporting the Inbound routes and extensions and some other stuff. I also fixed the provisioning links in the extensions. I wantd to do this so that I could provision everythgn ahead of time- get the softphones set up with the new server and deskphone configs ready to push out as well. When I restore the backup, will the old provisioning links be restored to the extensions? Will I hve to fix all those over again? Also, are there other caveats i need to be aware of when importing extensions and DIds ahead of time and then restoring the backup?

Thanks

 

[Saqqara]

FYI - you can not have two servers running at the same time with the same license and fqdn

When restoring a backup, it will wipe any existing settings and use the settings in the backup.

Normal procedure to transfer to new server.

1. Backup existing server with license and fqdn
2. Switch off server
3. Install 3cx on new server, restoring from step 1 backup

 

[phonecheese]

FYI - you can not have two servers running at the same time with the same license and fqdn

When restoring a backup, it will wipe any existing settings and use the settings in the backup.

Normal procedure to transfer to new server.

1. Backup existing server with license and fqdn
2. Switch off server
3. Install 3cx on new server, restoring from step 1 backup

I am using a different license and a different FQDN. The truth is, the only thing I really need to restore from backups seems to be the sound files for like voicemail and vm greetings etc.

Is there any way to just restore the voicemail and greetings? I suppose, worse comes to worse, I could just restore the backup and then import the DIDs and the extensions... I altered the export of the extensions so that the new Ip address shows up in the provisioning link.

 

[Naveen | Cal4care]

I am using a different license and a different FQDN. The truth is, the only thing I really need to restore from backups seems to be the sound files for like voicemail and vm greetings etc.

In this case you can take backup without "License Key Information, FQDN & Conference" and then follow the steps as Saqqara said.

If you change the FQDN, you have to re-provision all the end points(IP Phones & 3CX Clients).

 

[ChrisC_3CX]

@phonecheese

I altered the export of the extensions so that the new Ip address shows up in the provisioning link

Just want to clarify that if you're talking about the "InterfaceIP_0" column, you won't actually need to modify it as, upon import, it will be automatically replaced with whatever IP/FQDN is on the new 3CX Instance.

Also, a few things to bear in mind:

• If using a 3CX SBC, changing the FQDN will mean that you will have to redeploy the SBC as well.
• Since you'll be changing both FQDN and local IP, both Local and remote (STUN or SBC) IP Phones will need to be factory reset and reprovisioned.
• If using a Register based provider, make sure to disable all SIP Trunks on the old machine before deploying the new one.
• If using an IP Based provider and changing 3CX's Public IP as well, make sure you have informed the provider of this change.
• Remember to re-configure the firewall rules for the new 3CX Instance if you're managing the firewall.

 

[phonecheese]

@phonecheese


Just want to clarify that if you're talking about the "InterfaceIP_0" column, you won't actually need to modify it as, upon import, it will be automatically replaced with whatever IP/FQDN is on the new 3CX Instance.

Thanks, this is what I wanted to get clarified. Knowing that the backup getting restored will maintain the IP address under the InterfaceIP_0 column makes it so I don't have to import the altered extensions.csv again. I wish there was a way to export and import all the audio files rather than having to restore a backup to do this.

Also, I am using IP for authentication on my SIP trunks. Since this is the case, I assume there won't be a problem with keeping the original server up while I do a backup restore to the new server. Is this assumption correct?

Thanks

 

[ChrisC_3CX]

Knowing that the backup getting restored will maintain the IP address under the InterfaceIP_0 column makes it so I don't have to import the altered extensions.csv again

Sorry if I was unclear, the interface will not maintain the previous IP, it will be replaced with the IP set on the new 3CX Instance on which the backup is restored., meaning the provisioning link will be changed for local IP Phones.

Also, I am using IP for authentication on my SIP trunks. Since this is the case, I assume there won't be a problem with keeping the original server up while I do a backup restore to the new server. Is this assumption correct?

Provided that you are indeed using a different License key for the new machine then there should not be a problem.

 

[phonecheese]

Sorry if I was unclear, the interface will not maintain the previous IP, it will be replaced with the IP set on the new 3CX Instance on which the backup is restored., meaning the provisioning link will be changed for local IP Phones.


Provided that you are indeed using a different License key for the new machine then there should not be a problem.

No, you were perfectly clear. This is exactly what I wanted. Yes we are using a new license key (old one was standard, this one is professional).

Thanks alot for the help/info!

 

[ChrisC_3CX]

You're very welcome! Do let us know how it goes!