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-14172mariabackup doesn't store innodb_fast_checksum (removed variable) in backup-my.cnf when taking backup of 5.5
Closed
MDEV-14174crash on start with innodb-track-changed-pages
Closed
MDEV-14175backup shows corruption for 5.5 Server with innodb-fast-checksum
Closed
MDEV-14176XtraDB files with innodb_page_size in MariaDB 5.5 are incompatible with later versions
With environs framework I did following actions to deploy tar packages and run xtrabackup tests with then:
./replant.sh m2-10.0.30
m2-10.0.30/download.sh
./replant.sh m3-5.5.55
m3-5.5.55/download.sh
./replant.sh m6-10.1.23
m6-10.1.23/download.sh
# first test 10.1.23 alone just in case
./runsuite.sh m6 _plugin/xtrabackup/t
...
Duration=345
Passes=136
Failures=0
# now test 10.0.30 with mariabackup from 10.1.23
./runsuite.sh m6 m2 _plugin/xtrabackup/t
…
Duration=281
Passes=132
Failures=4
# now test 5.5.55 with mariabackup from 10.1.23
./runsuite.sh m6 m3 _plugin/xtrabackup/t
...
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
Andrii Nikitin (Inactive)
added a comment - - edited With environs framework I did following actions to deploy tar packages and run xtrabackup tests with then:
. /replant .sh m2-10.0.30
m2-10.0.30 /download .sh
. /replant .sh m3-5.5.55
m3-5.5.55 /download .sh
. /replant .sh m6-10.1.23
m6-10.1.23 /download .sh
# first test 10.1.23 alone just in case
. /runsuite .sh m6 _plugin /xtrabackup/t
...
Duration=345
Passes=136
Failures=0
# now test 10.0.30 with mariabackup from 10.1.23
. /runsuite .sh m6 m2 _plugin /xtrabackup/t
…
Duration=281
Passes=132
Failures=4
# now test 5.5.55 with mariabackup from 10.1.23
. /runsuite .sh m6 m3 _plugin /xtrabackup/t
...
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
With InnoDB plugin, 10.0.30 and 5.5.55 have less failures because some tests don't run . Crashes for incremental backup for mariabackup in 5.5.55 are still observed even with innodb plugin.
Andrii Nikitin (Inactive)
added a comment - The same tests with InnoDB plugin:
mkdir m2-10.0.30 /config_load
cp m2-10.0.30 /configure_innodb_plugin .sh m2-10.0.30 /config_load/
. /runsuite .sh m6 m2 _plugin /xtrabackup/t
...
FAILED tests :
_plugin /xtrabackup/t/remote_tablespaces .sh
Duration=215
Passes=127
Failures=1
mkdir m3-5.5.55 /config_load
cp m3-5.5.55 /configure_innodb_plugin .sh m3-5.5.55 /config_load/
. /runsuite .sh m6 m3 _plugin /xtrabackup/t
...
Duration=151
Passes=108
Failures=8
. /runsuite .sh m3 x9 _plugin /xtrabackup/t
...
Duration=143
Passes=117
Failures=0
With InnoDB plugin, 10.0.30 and 5.5.55 have less failures because some tests don't run . Crashes for incremental backup for mariabackup in 5.5.55 are still observed even with innodb plugin.
Please make sure all real failures (those that aren't caused by the tool/environment) are filed as separate bugs in JIRA/MDEV. It was desirable before the release, but after it's gone public it's mandatory.
Elena Stepanova
added a comment - anikitin ,
Please make sure all real failures (those that aren't caused by the tool/environment) are filed as separate bugs in JIRA/MDEV. It was desirable before the release, but after it's gone public it's mandatory.
10.0 tests all passed except xb_incremental_compressed_bitmap* , which is probably cannot run in 10.0
Related documentation request as been opened MDEV-14177
FAILED tests :
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_16kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_2kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_4kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_8kb.sh
Host=UBINTI
Extra=
Concurrency=10
Timeout=300
Duration=197
Passes=111
Failures=4
Andrii Nikitin (Inactive)
added a comment - 10.0 tests all passed except xb_incremental_compressed_bitmap* , which is probably cannot run in 10.0
Related documentation request as been opened MDEV-14177
FAILED tests :
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_16kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_2kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_4kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_8kb.sh
Host=UBINTI
Extra=
Concurrency=10
Timeout=300
Duration=197
Passes=111
Failures=4
Task
Major
MDEV-14172 mariabackup doesn't store innodb_fast_checksum (removed variable) in backup-my.cnf when taking backup of 5.5
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=345Passes=136Failures=0# now test 10.0.30 with mariabackup from 10.1.23…Duration=281Passes=132Failures=4# now test 5.5.55 with mariabackup from 10.1.23...Duration=162Passes=112Failures=17Failures 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