Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
11.4
Description
from: MDEV-36201?
$ mariadb-backup --prepare --export --target-dir=/bitnami/mariadb/backuptest
|
..
|
[00] 2025-02-28 11:29:35 Prepare export : executing "/opt/bitnami/mariadb/bin/mariadb-backup" --mysqld --defaults-file=./backup-my.cnf --defaults-group-suffix= --datadir=. --innodb --innodb-fast-shutdown=0 --loose-partition --innodb-buffer-pool-size=104857600 --console --log-error= --skip-log-bin --bootstrap < mariabackup_prepare_for_export.sql
|
|
|
|
mysqld: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb-backup' instead
|
|
[00] 2025-02-28 11:29:36 completed OK!
|
According to the above output, an invocation of mariadb-backup seems to wrongly complain about a deprecated program name mysqld. This seems to be something that would need to be fixed, possibly in extra/mariabackup/xtrabackup.cc.
Attachments
Issue Links
- relates to
-
MDEV-36201 InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT on mariadb-backup prepare
-
- Open
-