Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-6236

Admin-friendly scheduled backups

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Compared to dedicated backup software, Crucible's handling of scheduled backups is simplistic: their status is not stored anywhere (FE-1539), no notifications are sent if they fail (CRUC-5677), and if left unchecked, they could fill up disk space (CRUC-3106).

      And mere presence of a backup is not a guarantee that it's complete – there was at least one case where backup would not contain all requested data: CRUC-2752

      I propose to

      • store the status (OK/Failed/Warnings) and execution log of every backup job
      • expose those in the UI
      • send (configurable) e-mail notifications (f.e. if status was not OK)
      • allow the admin to delete old backups from UI

      Current workaround is to monitor log file for certain error messages, f.e.

      "BackupJob-execute - Error performing backup:"
      "Caches will NOT be included in this backup."

      Attachments

        Activity

          People

            Unassigned Unassigned
            d98344f3942d Sergey Svishchev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: