Backup takes a long time

[Alexandre Peloquin]

I have a client who has over 100 million call history. When we do a backup without the recordings, it takes between 4 and 6 hours to do and the backup to 8.05 GB. We want to migrate the 3CX to another server and we imagine that the restore should take as long if not longer. We only have a 9 hour maintenance window because my client is open 7 days a week.

We also cannot purge the calls logs because they have contracts with the government and they have to keep them.

We tried the Clear Call Logs in Custom Report Settings to remove older Call Logs however it doesn't seem to work.

Do you have any solutions so that we can succeed in our migration within 9 hours without deleting all the call logs?

Can we optimize the backup?

Thank you for your help.

 

[VasilisV_3CX]

Hi @Alexndre,

What you could do as a risk free test, would be to create a Passive Failover server and schedule a scheduled backup and restore to test your time window. If you fall outside of the window, you don't switch to the passive and no harm done, for now. This would give you an accurate expectation of your time frames with regards to backup and restore.

• Enable Failover on the Active server (provided they have an ENT key)
• Install a clean 3CX instance on the passive server
• Make sure the public IP will be the same for Active and Passive server
• Schedule the backup and restore within your maintenance window (allow 4-5 hours between backup start and restore start)
• If the restore is completed within the window, you can disable the active server and the passive will take over
• Remove failover on the passive server
• Optional: If you have local IP Phones/endpoints, you could stop the 3CX Services, change the LAN IP of the "new" server to that of the old one, then start service again so that the devices re-register.