Backnix

Consistent database backups for MySQL, MariaDB and PostgreSQL

Your database is usually the most valuable and the most fragile part of your infrastructure. Backnix is designed to create consistent backups with the native tools of each engine, then compress, encrypt and store them offsite.

Compare storage plans

The problem

The problem: a copied data directory is not a backup

Databases keep data in memory, write to several files at once and rely on transaction logs. Copying the data directory of a running server, or a dump taken without a consistent snapshot, can capture tables in different moments of time. The file looks fine until you try to restore it.

  • Inconsistent snapshots

    Orders without customers, invoices without items, or tables that fail to import.

  • Large dumps

    Backups that take hours can lock tables or slow down production if done the wrong way.

  • No point-in-time recovery

    A nightly dump alone cannot bring back the transactions made between the backup and the incident.

The consequence

The consequence: losing the transactions that matter most

When a database cannot be restored, the business loses its most recent and most valuable information: today's sales, new sign-ups, payments and support history. Even a successful restore of an old backup means re-entering data or explaining to customers why it disappeared.

The solution

How Backnix approaches database backup

Backnix is designed to run the right tool for each engine with consistency options enabled, stream the result through compression and client-side encryption, and upload it to S3 storage. Backups are tracked per database so you can see age, size and status at a glance.

  • MySQL and MariaDB

    Transactional logical dumps for InnoDB tables, with physical backup tools as an option for large datasets.

  • PostgreSQL

    pg_dump for logical backups and support for WAL-based strategies when point-in-time recovery is required.

  • Compression and encryption

    Dumps compress very well; encryption happens before the data leaves the server.

Database backup flow: MySQL, PostgreSQL or MariaDB produce a consistent backup that is compressed, encrypted and stored in S3.
Database backup flow: MySQL / PostgreSQL / MariaDB → Consistent Backup → Compression → Encryption → S3.

The diagram shows the designed architecture; availability is listed below.

Benefits

Benefits

  • Restorable by design

    Consistency options are part of the backup, not an afterthought.

  • Separate from file backups

    Databases get their own schedule, retention and alerts.

  • Smaller storage footprint

    Compressed logical backups typically use a fraction of the original data size; the exact ratio depends on your data.

  • Clear restore path

    Know which backup to use and how to load it before an incident happens.

Technical considerations

Why consistent backups matter

For InnoDB tables, mysqldump --single-transaction and mariadb-dump --single-transaction read all tables from one consistent snapshot without blocking writes. MyISAM tables do not support transactions and need locking. PostgreSQL's pg_dump always works on a consistent snapshot. For very large databases or point-in-time recovery, physical backups (Percona XtraBackup, MariaDB Backup, pg_basebackup) combined with binary logs or WAL archives are the better fit. Whatever the method, test restores regularly.

Availability

Current status of these capabilities

  • MySQL Backup

    Consistent MySQL backups using native tools.

    Coming soon
  • MariaDB Backup

    Consistent MariaDB backups using native tools.

    Coming soon
  • PostgreSQL Backup

    PostgreSQL backups with pg_dump and WAL-based strategies.

    Coming soon
  • Automated Backup Scheduling

    Run backups automatically on a schedule.

    Coming soon

Status is updated as capabilities are released. See all features.

Related articles

Learn more

Database backup FAQ

Will backups lock my tables?
With InnoDB and a single-transaction dump, normal reads and writes continue. MyISAM tables require locks during the dump.
Can I restore to a specific moment?
Point-in-time recovery requires binary logs (MySQL/MariaDB) or WAL archives (PostgreSQL) in addition to a base backup. Our articles explain how to set it up.
Do you support managed databases?
Managed services usually have their own snapshot features. Backnix focuses on databases you run on your own servers or containers.
Which versions are supported?
Supported engine versions will be published with the release of each database integration.

Ready to protect these systems?

Compare storage plans in USD or BRL. Yearly plans include 50% off the first annual payment.

View Pricing Talk to us
Talk to us

Get in touch about your environment

Tell us what you need to protect. We will answer by email; nothing is charged.