🗄 MySQL & MariaDB ⚡ Table-Level Incremental 🔐 Password Stays With You 🔒 Immutable (WORM) 🗄 MySQL & MariaDB ⚡ Table-Level Incremental 🔐 Password Stays With You 🔒 Immutable (WORM)
Database Backup

Back Up Your MySQL Database Automatically
No Shared Password, Table-Level Incremental

Your site's content is not in its files — it is in the database: orders, members, comments, settings. Yedekalma dumps it on your own server, encrypts it and sends it directly to your cloud storage. Your database password stays with you and you never open a MySQL port to the internet.

No credit card required · 14-day free trial

The Overlooked Risk

A File Backup Alone Is Not Enough

Restore the files but lose the database and all you have is an empty theme.

🛒

Orders and customers

In ecommerce, orders, customers and stock live entirely in the database.

📝

Content and pages

Posts, pages, categories and menus are database-stored, not in theme files.

👥

Users and permissions

Accounts, roles and password hashes are database-only.

💬

Comments and form entries

Years of accumulated comments and form submissions exist only in the dump.

⚙️

Settings and plugin data

Site settings, plugin configuration and licence records live in the database.

💥

Corrupted tables

A crash or disk fault can corrupt a table; without a clean dump, repair is often impossible.

Details

What Makes the Database Backup Different

Table-level incremental

Each table's checksum is compared and only changed tables are dumped. On large databases this cuts both time and storage dramatically.

🗄

Multiple databases

If your site uses several databases each is dumped separately — identically named databases on different hosts never collide.

🔐

Credentials stay local

MySQL credentials live in the module's encrypted secret store; they are never sent to our panel in plain text.

🔁

Remap on migration

When restoring you can remap the target database and have your configuration file updated automatically.

🦠

Malware scanning

Dumps can be scanned for injected malicious content so you know which restore point is clean.

🔎

Inspect before restoring

Browse the backup contents from the panel and examine tables before you commit to a restore.

Honest limits

The database component covers MySQL and MariaDB. PostgreSQL, MongoDB and SQL Server are not supported — we say so plainly rather than implying broader coverage.

We never alter backed-up data: no masking, no truncation, no anonymisation. The dump is a faithful copy of the source, so a restore returns your database exactly as it was.

FAQ

Database Backup — Frequently Asked Questions

No. The module that produces the dump runs on your own server and connects to the database locally. Your MySQL username and password stay in the module's encrypted secret store and are never sent to our panel in plain text. You also do not need to expose a MySQL port to the internet.
Not necessarily. With table-level incremental backups each table's checksum is compared and only changed tables are dumped. If your orders table changes hourly while your settings table has not changed in months, only the changed part is transferred.
Each one is dumped separately. Databases with the same name on different hosts are kept apart so their dumps never overwrite one another.
Yes. During restore you can remap the target database details, and your site's configuration file connection settings are updated accordingly. This is how server and hosting migration is handled.
Yes. It is compressed and encrypted with AES-256 on your own server — optionally with your own key (BYOK). The encrypted file goes straight to your storage target and never passes through our servers.

Protect Your Database Today

Files, database and email in one panel. 14 days free, no credit card.

Create Free Account

See the four-step setup →