mariadb-backup vs Medusa

mariadb-backup is a free, open-source tool for physical backups of MariaDB tables, including while the server is running. Available on Linux and Windows for self-hosted deployments, it supports InnoDB, Aria, MyISAM, and MyRocks. Backup options include full, incremental, and partial copies, point-in-time recovery, and restoration of individual databases, tables, or partitions. It can make hot online InnoDB backups and uses a nearly non-blocking method for full backups on running systems. It also supports Galera Cluster state snapshot transfers, InnoDB page-compressed tables, and tables protected by data-at-rest encryption; encrypted tables stay encrypted in the backup. Output can be streamed to stdout for piping to tools such as OpenSSL or gzip. Restoring requires preparation with the --prepare option, and safe full or incremental restores require an empty MariaDB data directory. Backup operations connect to the running server and generally require global RELOAD, PROCESS, LOCK TABLES, and BINLOG MONITOR privileges. The listed plan is free.

Medusa is a command-line backup system for Apache Cassandra that runs on Linux in a self-hosted deployment. It supports full and differential backups, single-node backup and restore, and cluster-wide restores in place or to a remote location. Backup destinations include local storage, Google Cloud Storage, Azure Blob Storage, AWS S3, and compatible S3 services. It supports clusters using either single tokens or vnodes. Its verify command checks backup completion, manifest and file presence, and file hashes; MD5 checks can be enabled, while file size is checked by default. Configuration documentation covers client SSL settings and S3 server-side encryption with KMS or customer-provided keys. Retention settings can purge backups by age or count. Installation instructions cover pip and Debian packages, including offline installation, and describe installing Medusa on each Cassandra node. It requires Python 3.9 or newer and is licensed under Apache-2.0. A stated constraint is that it does not support Cassandra deployments with multiple data-folder directories.