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

Backup to several destinations stops when one of them fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 15.0.17.32
    • Fix Version/s: None
    • Component/s: Backup & Restore
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.6.1
    • Distro Version:
      Linux Raspbx 4.19.75-v71+
    • Distro:
      Other
    • Module Fix Version:

      Description

      I have backups scheduled to several destinations :

      • local
      • ftp on our LAN
      • ftp in the cloud

      When one destination fails, the process stops and the scheduler does not try the other destinations. The log indicates :

      ERROR : open( ............) failed to open ..........

      INFO :  Finished Saving to selected filestore locations.

      This is wrong, when the first fails the other locations are not tried (no mention in the log, nothing saved in the FTP locations ). Presently the first failed sometimes for failed to open stream : No such file or directory. This is strange, but this is another issue.

      Since this bug is not so easy to reproduce, I join a detailed description of the tests I did this evening.

       

      My version of Backup and Restore is 15.0.10.61 . This is different from what I indicated in the list, because this version was not proposed.

      I am running RasPBX on a Raspberry PI 4

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dysmas dysmas
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:

                  NextupJiraPlusStatus

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