I am using 2x boxes running FreePBX 13. They are setup in a Warm Spare config. When the Backup is initiated from the Warm Spare, the backup from remote server (primary) works alright, the tar file is available on the warm spare server as well, CDR db is restored correctly too, and overall reports a successful backup, but the /etc/asterisk files are not getting restored (though they are present in the tar file).
This seems to be stemming from an error reported in the logs, that can be seen in the enclosed image.
Now, please NOTE that this is not on an x86-platform but on an ARM-platform and one key difference is that on this platform, the SysAdmin module is not supported. Hence, I believe the Restore is broken and missing some steps from the Restore sequence.
I am trying to understand,
Why the SysAdmin module is needed for a Backup & Restore cycle for Warm Spare but not needed for local Backup & a local Restore.
A way to avoid those sequence of steps during Restore (in Warm Spare scenario) that have a dependency on the SysAdmin module.
Is that possible? Has anyone tried? My early thoughts are, if the customization isn’t possible, then perhaps using a post-backup hook or a script that can complete the remaining tasks after the Restore steps fail (though it reports success).
Any insight on customizing the Backup and Restore module for the Warm Spare config will be extremely helpful. Thanks.