mariadb-backup

mariadb-backup is an open-source, self-hosted utility for physical online backups of MariaDB tables. It is aimed at database administrators who need engine-aware backup and recovery rather than a hosted control panel. The zero-cost plan is attractive, but successful restoration depends on careful preparation, privileges, and destination handling.

Overview

The tool connects to a running MariaDB Server for backup operations; restore work does not require a database user. It supports full, incremental, and partial backups, point-in-time recovery, and restoration of individual databases, tables, and partitions. That range suits both routine protection and selective recovery, provided your team is comfortable managing backup files and recovery sequences.

Online operation is a practical strength. Full backups use a nearly non-blocking approach on running systems, while InnoDB supports hot online backups. This fits production services where stopping MariaDB for a conventional copy would be disruptive. It is still an infrastructure utility, not a guided backup dashboard for non-specialists.

Key features

Flexible backup and recovery

Full backups establish a complete baseline; incremental backups reduce the amount of data captured after that baseline; and partial backups let you target narrower selections. Point-in-time recovery gives administrators a way to recover to a chosen moment, while individual database, table, and partition restoration supports more focused incidents. Partial backups require many steps and cannot be restored directly onto an existing server that contains other data, so they are best for operators who can control the destination environment.

Engine and cluster coverage

Support spans InnoDB, Aria, and MyISAM, with backup and restore support for MyRocks. The tool can also provide Galera Cluster state snapshot transfers (SSTs), making it relevant to clustered MariaDB deployments rather than only standalone servers. InnoDB page-compressed tables are supported during backup and restore.

Encryption and streaming

Data-at-rest encrypted tables remain encrypted in the backup. mariadb-backup can load the server's key-management and encryption plugin to handle those tables. Output can stream to standard output, allowing pipelines to OpenSSL or gzip when you need encryption or compression outside the backup process itself.

Restore discipline

Every backup must be prepared with the --prepare option before restoration, making its files point-in-time consistent for MariaDB Server. Safe full and incremental restores require an empty MariaDB data directory. These requirements protect consistency but add operational steps that automated, hosted products often hide.

Privileges and access

Backup operations generally need global RELOAD, PROCESS, LOCK TABLES, and BINLOG MONITOR privileges. MariaDB recommends a dedicated account with those backup privileges. Restore operations do not require a database user, which simplifies work on an offline or newly prepared destination.

Pricing

The Open-source mariadb-backup plan costs free. It covers physical backups for MariaDB data on Linux and Windows. There are no paid tiers, seat charges, storage quotas, or trial terms in this plan. The trade-off is that the product supplies a command-line, self-hosted capability rather than a hosted service with managed storage or a visual scheduling layer.

Platforms

mariadb-backup runs on Linux and Windows, with a self-hosted deployment model. It is designed for MariaDB Server using InnoDB, Aria, MyISAM, or MyRocks storage engines, so platform choice should follow where your database infrastructure already runs.

Who it's for

Choose it if you administer MariaDB directly, need online protection for active systems, or require incremental, partial, point-in-time, encrypted, and engine-specific recovery options without licensing cost. It is particularly suitable for teams operating Galera clusters or mixed MariaDB storage engines.

Look elsewhere if you want a hosted backup service, a graphical workflow, or restores that do not require preparing files and clearing the target data directory. The privilege model and multi-step partial-restore process also make it a poor fit for occasional users without database administration experience.

Pros and cons

• Pro: Nearly non-blocking full backups and hot InnoDB operation reduce maintenance interruption on live systems.
• Pro: Full, incremental, partial, and point-in-time options cover routine, selective, and time-specific recovery.
• Pro: InnoDB, Aria, MyISAM, MyRocks, Galera SST, encrypted tables, and page-compressed tables broaden deployment coverage.
• Pro: Standard-output streaming works with OpenSSL and gzip for external encryption or compression pipelines.
• Con: Backups must be prepared before restore, adding a required consistency step.
• Con: Full and incremental restores need an empty data directory, complicating in-place recovery.
• Con: Partial backups are laborious and cannot be restored directly onto servers that already contain other data.
• Con: Backup privileges and self-hosted file management demand experienced operators.

Alternatives

For a broader database directory, see Database Backup Software. Choose MySQL instead when you need a freemium database platform spanning Linux, macOS, Windows, API, and self-hosted deployments, with a free trial and replication and high-availability components. DBDock is a free, MIT-licensed self-hosted CLI alternative. Quemsi suits users wanting a freemium, open-source agent with an unlimited-database Solo plan. SqlBak is the better fit for a managed-style workflow with web access, alerts, and a free tier limited to one server, two databases, and one month of history. Databasus offers free Apache 2.0 software across Linux, self-hosted, and web deployments. DBAegis targets PostgreSQL administration with a Community plan limited to one admin, three connections, and three schedules. Percona Backup for MongoDB is the relevant free, self-hosted choice for MongoDB rather than MariaDB. pg_probackup is a free backup and recovery utility for PostgreSQL clusters.

Verdict

mariadb-backup is the right choice for MariaDB administrators who want comprehensive physical, online, and engine-aware recovery controls at no license cost. Its main reason to choose it is the combination of hot InnoDB backups, point-in-time recovery, encryption handling, and broad engine support. Look elsewhere when your priority is a hosted interface, simpler restores, or a workflow that does not require prepared files, an empty destination directory, and database-level operational expertise.