[MDEV-32994] more clear error message when trying to prepare mariadb-backup taken by different version originally Created: 2023-12-12  Updated: 2023-12-29

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Hartmut Holzgraefe Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None


 Description   

When taking a backup with mariabackup/mariadb-backup with one version of the tool, but trying to prepare it with a later version, the --prepare run will fail with e.g.:

mariabackup based on MariaDB server 10.5.15-10-MariaDB debian-linux-gnu (x86_64)
 
[00] 2023-12-12 02:40:03 cd to /root/backup_2023-12-11/
 
[... some 15+ lines of server/engine initialization messages ...]
 
2023-12-12  2:40:03 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with Backup 10.4.30-MariaDB.
 
2023-12-12  2:40:03 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
 
[00] FATAL ERROR: 2023-12-12 02:40:03 mariabackup: innodb_init() returned 11 (Generic error).

This should report way more clearly that the backup can only be prepared using a mariadb-backup binary of the same major version as the server was running at the time the backup was taken, e.g.:

[FATAL ERROR] This is a backup of a server running a different MariaDB major version (10.4) than that of this mariadb-backup binary (10.5). Backups can only be prepared when the major version both match, so you'd need an older mariadb-backup binary installation from a 10.4 release for this task.


Generated at Thu Feb 08 10:35:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.