Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-9123

Backup from HA cluster doesn't restore to a non-HA FreePBX server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Backup & Restore
    • Environment:

      FreePBX 12.0.54 with Asterisk 11.16.0
      Backup & Restore module version 12.0.15

    • ToDo:
    • Asterisk Version:
      11.16.0
    • Distro Version:
      12.0.54
    • Distro:
      FreePBX Distro

      Description

      I was following the easily found instructions to create a warm spare backup PBX by establishing an SSH key between it and the main PBX to pull backups and restore to itself. This is so the spare is always a day or less behind the primary's configuration, making failover quicker in the event of an outage.

      What I have noticed, however, is when backing up an HA cluster (Schmoozecom commercial HA module with licensing) and restoring it to the warm spare, it doesn't restore correctly.

      After suspecting this to be due to the nature of an HA cluster having the asterisk/freepbx/etc directories moved to /drbd/ and symbolic links created in their place, I wrote a shell script to modify the warm spare to allow backups to work.

      However, can the Backup & Restore module be updated to not require a script as I just mentioned? I'll attach my script for reference.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                xrobau Rob Thomas
                Reporter:
                brumar59 brumar59
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.