[MDEV-14963] mariabackup is not included in MariaDB-server package Created: 2018-01-16  Updated: 2018-01-17  Resolved: 2018-01-16

Status: Closed
Project: MariaDB Server
Component/s: Backup
Affects Version/s: 10.2.12
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS Linux release 7.4


 Description   

mariabackup is not included in MariaDB-server package

mysqldump tool for example comes with MariaDB-server package and it would be expected
the mariabackup to be included too

how to repeat
install MariaDB-server
check for mariabackup toll -it's not present and has to be installed additionally

[root@t4w5 ~]# mariabackup
-bash: mariabackup: command not found

 Comments   
Comment by Elena Stepanova [ 2018-01-16 ]

https://mariadb.com/kb/en/library/mariadb-backup-overview/#installing-on-linux

MariaBackup is a separate package, it's intentional, there are several reasons for that:

  • mariabackup went through a separate release cycle, so it was alpha/beta when the rest of the server was already stable;
  • mariabackup could have additional dependeincies which the server doesn't, we don't want to impose them on people who don't need the backup;
  • users might want to install mariabackup with a different version of the server, they shouldn't need to install the whole server for that (and they wouldn't be able to, neither deb nor rpm packaging allows to have different MariaDB servers in parallel).

It should be included in the binary tarball though, if it's not, it might be a bug.

Comment by Zdravelina Sokolovska (Inactive) [ 2018-01-17 ]

RE
– that issue is just a request
– users of server probably would need backup tool; respectively users of MariaDB-server might be interested in MariaDB-backup; any special dependences was not seen during the installation of MariaDB-server
– may have mariabackup as separate package ; but also to be included in MariaDB-server pack;

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