Solved Scheduled Backup Won't Start Issue

[Leo_B]

Hello,

Back on Monday we have switched all our 3CX instances backup tasks to Google Storage instead of SFTP location. As of Wednesday, two PBX setups scheduled backups appear to work seamlessly, while the other two ones show no signs of backup start despite the basically identical settings both in 'Location' and 'Backup Schedule' tabs. Tweaking the schedule time gives no result as 3cxSystemService.log lists BackTrigger changed only. No 'Backup started' event displayed and no backup error notification received.

What was done:

- checked the current date/time, date command output is 100% correct
- disabled the Scheduled backup, then enabled it again, set the backup time, no progress
- tried to backup the PBX instance manually, worked like a charm

Any suggestions?

3CX Version: Enterprise Annual 16.0.1078
Server OS: Debian 9 v16.0.655
Is the 3CX Server Hosted: no
IP Phone Make/Model/Firmware: Yealink T58A v58.85.0.5
Provisioning Method: SBC
Trunk Provider: Vitelity
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO

 

[ChrisC_3CX]

Have you followed this guide to set it up: https://www.3cx.com/docs/google-cloud-storage/
Do upgrade the 3CX PBX to the latest version as well(16.0.8.9).


Also:
• Are you using the same project for all 3CX PBXs or a separate project for each PBX?
• Is this a VM or a physical machine? If a VM, where is it hosted and on what Hypervisor?
• Try disabling IPv6 on this machine. We have had reports where having IPv6 enabled would cause the connection to drop.

 

[Leo_B]

Have you followed this guide to set it up: https://www.3cx.com/docs/google-cloud-storage/
Do upgrade the 3CX PBX to the latest version as well(16.0.8.9).


Also:
• Are you using the same project for all 3CX PBXs or a separate project for each PBX?
• Is this a VM or a physical machine? If a VM, where is it hosted and on what Hypervisor?
• Try disabling IPv6 on this machine. We have had reports where having IPv6 enabled would cause the connection to drop.

Thank you for response! In a nutshell, we use one Google Storage instance, different folders, both Vultr-hosted VMs have no issues with accessing the ones. Last night we resolved the scheduled backups problem just by restarting the on of the PBXs affected. Still have to do the same trick with the other one and check the PBX capability to run scheduled backups nightly as well. I will update this thread on Friday's morning.

 

[Leo_B]

Monday's update: yes, VM reboot trick worked for both 3CX setups which trigger and launch the nightly backups seamlessly. Still cannot understand, though, what was the reason for the problem.

 

[AWS2P]

Murphy's law ?

 

[Leo_B]

Murphy's law ?

It is!

 

[VasilisV_3CX]

Glad to managed to solve this @Leo_B, if you require any further assistance feel free to open a new thread.