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

implement --innodb-track-changed-pages

Details

    Description

      The feature is critical for quick incremental backups (e.g. of huge tables).

      (Xtradb has this feature, which allows quick incremental backups with mariabackup 10.1 ).

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-10798 Implement ALL user statements for handling xtradb changed page bitmaps (xdb files)

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-14992 BACKUP: in-server backup

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Task - A task that needs to be done. MDEV-12472 InnoDB should accept XtraDB parameters, warning that they are ignored

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            ralf.gebhardt Ralf Gebhardt added a comment -

            I have removed the fixVersion for this task as it is one of 5.5, 10.1, 10.2, 10.3, which are EOLed.

            Please add a new fixVersion if you plan to work on this task for a not EOLed versions.

            ralf.gebhardt Ralf Gebhardt added a comment - I have removed the fixVersion for this task as it is one of 5.5, 10.1, 10.2, 10.3, which are EOLed. Please add a new fixVersion if you plan to work on this task for a not EOLed versions.
            marko Marko Mäkelä added a comment -

            This could be considered as part of MDEV-14992.

            A trivial way of implementing this would be to just use the InnoDB redo log, and implement something like

            SET GLOBAL innodb_log_file_archive=@@last_backup_end_lsn;

            so that any log that was written since the last successfully completed backup would be archived, and an incremental backup based on simply copying that log would be possible.

            Ideally, I would remove other types of executing incremental backup.

            marko Marko Mäkelä added a comment - This could be considered as part of MDEV-14992 . A trivial way of implementing this would be to just use the InnoDB redo log, and implement something like SET GLOBAL innodb_log_file_archive=@@last_backup_end_lsn; so that any log that was written since the last successfully completed backup would be archived, and an incremental backup based on simply copying that log would be possible. Ideally, I would remove other types of executing incremental backup.

            People

              marko Marko Mäkelä
              anikitin Andrii Nikitin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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