Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-19246

Change database and table used for Mariabackup's history

Details

    Attachments

      Issue Links

        Activity

          GeoffMontee Geoff Montee (Inactive) created issue -
          GeoffMontee Geoff Montee (Inactive) made changes -
          Field Original Value New Value
          GeoffMontee Geoff Montee (Inactive) made changes -
          Assignee Vladislav Vaintroub [ wlad ]
          GeoffMontee Geoff Montee (Inactive) made changes -
          Assignee Vladislav Vaintroub [ wlad ] Vladislav Lesin [ vlad.lesin ]
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          Assignee Vladislav Lesin [ vlad.lesin ] Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s 10.4 [ 22408 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Epic/Theme MariaDB_Branding
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s 10.7 [ 24805 ]
          Priority Major [ 3 ] Critical [ 2 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Assignee Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]
          GeoffMontee Geoff Montee (Inactive) made changes -
          GeoffMontee Geoff Montee (Inactive) made changes -
          serg Sergei Golubchik made changes -
          Priority Critical [ 2 ] Major [ 3 ]
          julien.fritsch Julien Fritsch made changes -
          Assignee Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]
          serg Sergei Golubchik made changes -
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s 10.7 [ 24805 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Assignee Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 95359 ] MariaDB v4 [ 131061 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Assignee Sergei Golubchik [ serg ]

          is this table only used by mariabackup itself for incremental backups? Does it have any other usages, other tools that use it, perhaps?

          serg Sergei Golubchik added a comment - is this table only used by mariabackup itself for incremental backups? Does it have any other usages, other tools that use it, perhaps?
          serg Sergei Golubchik made changes -
          Status Open [ 1 ] Needs Feedback [ 10501 ]

          I am not aware of any tools other than Percona XtraBackup and mariabackup that use the table.

          According to the Percona XtraBackup documentation, the table is primarily intended for maintaining a history of backups for informational purposes:

          Percona XtraBackup supports storing the backups history on the server. This feature was implemented in Percona XtraBackup 2.2. Storing backup history on the server was implemented to provide users with additional information about backups that are being taken. Backup history information will be stored in the PERCONA_SCHEMA.XTRABACKUP_HISTORY table.

          https://www.percona.com/doc/percona-xtrabackup/LATEST/xtrabackup_bin/backup.history.html

          GeoffMontee Geoff Montee (Inactive) added a comment - I am not aware of any tools other than Percona XtraBackup and mariabackup that use the table. According to the Percona XtraBackup documentation, the table is primarily intended for maintaining a history of backups for informational purposes: Percona XtraBackup supports storing the backups history on the server. This feature was implemented in Percona XtraBackup 2.2. Storing backup history on the server was implemented to provide users with additional information about backups that are being taken. Backup history information will be stored in the PERCONA_SCHEMA.XTRABACKUP_HISTORY table. https://www.percona.com/doc/percona-xtrabackup/LATEST/xtrabackup_bin/backup.history.html
          GeoffMontee Geoff Montee (Inactive) made changes -
          Status Needs Feedback [ 10501 ] Open [ 1 ]
          ralf.gebhardt Ralf Gebhardt added a comment -

          But it is not only to log a history, XtraBackup can also use this history to for incremental backups

          ralf.gebhardt Ralf Gebhardt added a comment - But it is not only to log a history, XtraBackup can also use this history to for incremental backups
          serg Sergei Golubchik added a comment - - edited

          okay, if there aren't any tools that would break because of this change, then yet, let's do it.
          What should be the new name? mysql.mariabackup_history ?

          serg Sergei Golubchik added a comment - - edited okay, if there aren't any tools that would break because of this change, then yet, let's do it. What should be the new name? mysql.mariabackup_history ?
          ralf.gebhardt Ralf Gebhardt made changes -
          julien.fritsch Julien Fritsch made changes -
          Priority Major [ 3 ] Blocker [ 1 ]
          julien.fritsch Julien Fritsch made changes -
          Priority Blocker [ 1 ] Critical [ 2 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s 10.11 [ 27614 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Assignee Sergei Golubchik [ serg ] Alexander Barkov [ bar ]
          AirFocus AirFocus made changes -
          Description Mariabackup still uses the PERCONA_SCHEMA.xtrabackup_history table to store history:

          https://mariadb.com/kb/en/library/mariabackup-options/#-history

          https://github.com/MariaDB/server/blob/mariadb-10.4.4/extra/mariabackup/xtrabackup.cc#L1123

          https://github.com/MariaDB/server/blob/mariadb-10.4.4/extra/mariabackup/backup_mysql.cc#L584

          https://github.com/MariaDB/server/blob/mariadb-10.4.4/extra/mariabackup/backup_mysql.cc#L1439

          Maybe we should rename this database and table?
          Mariabackup still uses the PERCONA_SCHEMA.xtrabackup_history table to store history:

          https://mariadb.com/kb/en/library/mariabackup-options/#-history

          https://github.com/MariaDB/server/blob/mariadb\-10.4.4/extra/mariabackup/xtrabackup.cc#L1123

          https://github.com/MariaDB/server/blob/mariadb\-10.4.4/extra/mariabackup/backup\_mysql.cc#L584

          https://github.com/MariaDB/server/blob/mariadb\-10.4.4/extra/mariabackup/backup\_mysql.cc#L1439

          Maybe we should rename this database and table?
          bar Alexander Barkov made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          bar Alexander Barkov added a comment - Hello serg , Can you please review this patch: https://github.com/MariaDB/server/commit/24d3f2cb8037f40dfce4b6da7ca243c838aa9800 ? Thanks!
          bar Alexander Barkov made changes -
          Assignee Alexander Barkov [ bar ] Sergei Golubchik [ serg ]
          Status In Progress [ 3 ] In Review [ 10002 ]

          24d3f2cb8037f40dfce4b6da7ca243c838aa9800 is ok to push

          serg Sergei Golubchik added a comment - 24d3f2cb8037f40dfce4b6da7ca243c838aa9800 is ok to push
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ] Alexander Barkov [ bar ]
          Status In Review [ 10002 ] Stalled [ 10000 ]

          The primary name is mariadb-backup, but it'd be inconvenient to have a dash in the identifier (table name), it'd always need to be quoted. So mariabackup_history or maria_backup_history. And I think between those two either is fine.

          serg Sergei Golubchik added a comment - The primary name is mariadb-backup, but it'd be inconvenient to have a dash in the identifier (table name), it'd always need to be quoted. So mariabackup_history or maria_backup_history . And I think between those two either is fine.

          Let's go with mariadb_backup_history. It's closest possible to the program name, just using an underscore instead of a dash.

          bar Alexander Barkov added a comment - Let's go with mariadb_backup_history . It's closest possible to the program name, just using an underscore instead of a dash.
          bar Alexander Barkov made changes -
          Status Stalled [ 10000 ] In Progress [ 3 ]
          bar Alexander Barkov made changes -
          Fix Version/s 10.11.0 [ 28411 ]
          Fix Version/s 10.11 [ 27614 ]
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          AnneStrasser Anne Strasser (Inactive) made changes -
          AnneStrasser Anne Strasser (Inactive) made changes -
          mariadb-jira-automation Jira Automation (IT) made changes -
          Zendesk Related Tickets 201675
          Zendesk active tickets 201675

          People

            bar Alexander Barkov
            GeoffMontee Geoff Montee (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            9 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.