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

mariadb --prepare --export fails with "Upgrade after crash is not supported" and error 11

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4.13, 10.5.4
    • 10.5, 10.11
    • mariabackup
    • None
    • Ubuntu 20.04
      Google Cloud

    Description

      Customer reported following error when they tried to restore databases to a mariadb installation with version 10.5.4 installed with a backup taken from an instance running 10.4.13.

      I'm attempting to restore databases to a mariadb installation with version 10.5.4 installed with a backup taken from an instance running 10.4.13. I will paste a copy of the error at the end of this description. Is there some method to force mariabackup on the new installation to do a conversion or upgrade of the backup so it is able to properly use it for restoration?
       
      Here is the output of the attempted restoration job run:
       
      root@db-staging-primary-2:/opt/mariadb# mariabackup --prepare --export --target_dir=/opt/mariadb/backup-scratch
      mariabackup based on MariaDB server 10.5.4-MariaDB debian-linux-gnu (x86_64)
      [00] 2020-08-03 23:04:49 cd to /opt/mariadb/backup-scratch/
      [00] 2020-08-03 23:04:49 This target seems to be not prepared yet.
      [00] 2020-08-03 23:04:49 mariabackup: using the following InnoDB configuration for recovery:
      [00] 2020-08-03 23:04:49 innodb_data_home_dir = .
      [00] 2020-08-03 23:04:49 innodb_data_file_path = ibdata1:10M:autoextend
      [00] 2020-08-03 23:04:49 innodb_log_group_home_dir = .
      [00] 2020-08-03 23:04:49 InnoDB: Using Linux native AIO
      [00] 2020-08-03 23:04:49 Starting InnoDB instance for recovery.
      [00] 2020-08-03 23:04:49 mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      2020-08-03 23:04:49 0 [Note] InnoDB: Uses event mutexes
      2020-08-03 23:04:49 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-08-03 23:04:49 0 [Note] InnoDB: Number of pools: 1
      2020-08-03 23:04:49 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      mariabackup: O_TMPFILE is not supported on /tmp (disabling future attempts)
      2020-08-03 23:04:49 0 [Note] InnoDB: Initializing buffer pool, total size = 104857600, chunk size = 104857600
      2020-08-03 23:04:49 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-08-03 23:04:49 0 [Note] InnoDB: page_cleaner coordinator priority: -20
      2020-08-03 23:04:49 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with Backup 10.4.13-MariaDB.
      2020-08-03 23:04:49 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
      [00] FATAL ERROR: 2020-08-03 23:04:49 mariabackup: innodb_init() returned 11 (Generic error).
      

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              allen.lee@mariadb.com Allen Lee (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              13 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.