Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-5617

Analyze/Design Backup and Restore for enterprise manager.

    XMLWordPrintable

Details

    • MXS-SPRINT-235, MXS-SPRINT-236, MXS-SPRINT-237, MXS-SPRINT-238, MXS-SPRINT-239, MXS-SPRINT-240, MXS-SPRINT-241, MXS-SPRINT-242

    Description

      "GUI-driven backup configuration and scheduling, supporting full, incremental, differential, and logical backups (e.g., mariadb-dump)."

      This needs

      • a UI allowing a user to configure when and how backups should be run,
      • a mechanism for storing the entered configuration somewhere,
      • a mechanism that initiates backups at the configured time, and
      • a mechanism that actually executes the backup.

      Managing the backup configuration and initiating the backup operation seems to belong to the realm of SuperMax with MemaGUI handling the user interface, but the actual execution of the backup operation could be handled by SuperMax or the MaxScale, which is in front the server in question.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.