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

Missing *.cfg files with export option used in mariabackup (10.6.20)

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.20
    • 10.6
    • None
    • None

    Description

      We run a fully automated restore test that uses mariabackup for restoration. With the export option specified, *.cfg files should be generated. This works fine with version 10.6.19. However, starting with version 10.6.20, our restore tests are failing due to missing *.cfg files. Indeed, the *.cfg files are no longer generated in version 10.6.20.

      Attached, you’ll find the restore logs and the output of the database directory, listing some tables. The backup files and restore process are identical for both test runs; the only difference is the switch in MariaDB versions.

      Parts of our restore script used:

      echo "Preparing full backup..."
       
      /usr/bin/mariabackup --prepare --export --target-dir $RESTORE_TMP_PATH
       
      if [ -n "$INCREMENTAL_DIR" ]; then
      	echo "Extracting incremental backup..."
       
      	mkdir $RESTORE_TMP_PATH/$INCREMENTAL_DIR
      	gunzip -c $INCREMENTAL_DIR.gz | mbstream -x -C $RESTORE_TMP_PATH/$INCREMENTAL_DIR
       
      	echo "Preparing incremental backup..."
       
      	/usr/bin/mariabackup --prepare --export --target-dir $RESTORE_TMP_PATH --incremental-dir $RESTORE_TMP_PATH/$INCREMENTAL_DIR/
      fi
      
      

      Attachments

        1. 10.6.19-1.log
          153 kB
          Jens Wurster
        2. 10.6.20-1.log
          152 kB
          Jens Wurster

        Activity

          People

            marko Marko Mäkelä
            wursterje Jens Wurster
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.