Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
None
-
None
-
None
Description
The first version of MariaDB Backup was added to 10.1.23. As we now support also Windows we can expect to get questions from users/customers about supporting 10.0 and 5.5.
It would be good to test MariaDB Backup against the newest versions of MariaDB Server 5.5 and 10.0. and to add the information to the table https://mariadb.com/kb/en/mariadb/mariadb-backup/ in a "Compatibility" column
Attachments
Issue Links
- relates to
-
MDEV-14172 mariabackup doesn't store innodb_fast_checksum (removed variable) in backup-my.cnf when taking backup of 5.5
-
- Closed
-
-
MDEV-14174 crash on start with innodb-track-changed-pages
-
- Closed
-
-
MDEV-14175 backup shows corruption for 5.5 Server with innodb-fast-checksum
-
- Closed
-
-
MDEV-14176 XtraDB files with innodb_page_size in MariaDB 5.5 are incompatible with later versions
-
- Closed
-
-
MDEV-14177 Document comand FLUSH CHANGED_PAGE_BITMAPS
-
- Closed
-
-
MDEV-14937 Test final version of MariaDB Backup 10.1 against newest versions of 5.5 and 10.0
-
- Closed
-
With environs framework I did following actions to deploy tar packages and run xtrabackup tests with then:
# first test 10.1.23 alone just in case
...
Duration=345
Passes=136
Failures=0
# now test 10.0.30 with mariabackup from 10.1.23
…
Duration=281
Passes=132
Failures=4
# now test 5.5.55 with mariabackup from 10.1.23
...
Duration=162
Passes=112
Failures=17
Failures in 10.0 are in tests xb_incremental_compressed_bitmap* and rather internal problems of the framework, which needs to be adjusted to 10.0
Almost all failures in 5.5 are related to crashes of mariabackup during incremental backup.
Conclusion:
mariabackup 10.1.23 works “well enough” with 10.0.30 MariaDB Server
mariabackup 10.1.23 works “well enough” with 5.5.55 MariaDB Server, excluding incremental backup.
“Well enough” = considering Alpha status of the release