Scheduled Restore Issues

[outland]

Hello,
I have setup an Enterprise server with a second as a failover. Following the guide here: https://www.3cx.com/docs/failover/ (on-premise scenario A) and setting up split DNS following the guide here: https://www.3cx.com/docs/creating-fqdn-split-dns/. Phones are pointed to fqdn. During a failover, do I have to adjust internal DNS entry to point to passive server?

I have setup both servers to look at a single Google Drive location. Scheduled backups are working correctly and I can see the current backups on the passive server. However, the scheduled restore process is not working. There is nothing in the event log to depict why. Any thoughts on this? All help is appreciated. Thanks!!

 

[cobaltit]

As far as adjusting DNS unless you believe in magic, the answer is yes. The failover link you provided briefly mentions it and there are links at bottom to scripts for updating DNS.

No clue as to why the Google Drive restore isn't working. If this is a test setup it might be worth it to upgrade to the Update 5 beta as there were some API updates as far as Google Drive goes that might resolve that issue. Otherwise you would want to open a ticket with your partner or 3CX support directly

 

[YiannisH_3CX]

Hello @outland

Since the backups are visible in the passive server you should have issues restoring. The first thing to check is the time you set the restore to take place. The restore should take place after the backup has finished. Depending on the backup size this could take some time so make sure that the backup and the restore have sufficient time between them. Also check the activity log for any clues as to why this is happening.

 

[outland]

Thanks for the replies.

The schedule is setup on the passive server and for all that I can see should be kicking off. There is nothing in the activity log which indicates to me that the restore is not being triggered. The backups are currently around 300mb and when doing a manual restore it does not take long at all. I thought there was a way to trigger the restore from cmd line but what I found is for an older version. Thanks again!

 

[YiannisH_3CX]

Since everything looks properly configured and the scheduled restore still fails i would recommend creating a ticket with our support department so they can take a look at the issue and determine the cause.