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, can encrypt it (optional AES-256) and sends it directly to your cloud storage. Your database password stays with you and you never open a MySQL port to the internet.

🎁 Start Your Free Trial See Pricing

No credit card required · Current campaign: free until the end of the year

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

Optional: changes are tracked at table level and only changed tables are dumped, with a periodic full backup. On large databases this can save time and storage.

🗄

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 detection

An optional database scan (off by default) runs during backup on your server and reports injected scripts or hidden iframes — detection only — so you can pick a clean restore point.

🔎

Check before restoring

List the backup's contents from the panel, then choose which databases to restore in the 3-step wizard (component · summary · confirm) — or run verification only first.

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. Restores work per database; restoring a single table on its own is not supported.

FAQ

Database Backup — Frequently Asked Questions

Do I have to share my database password?

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.

Is the whole database dumped every time?

Not necessarily. If you turn on the optional incremental mode, changes are tracked at table level and only changed tables are dumped; a full backup still runs periodically. If your orders table changes hourly while your settings table has not changed in months, only the changed part is transferred. Where incremental is on, that component gets a discount.

What if I have more than one database?

Each one is dumped separately. Databases with the same name on different hosts are kept apart so their dumps never overwrite one another.

Can I restore to a different server?

Yes, as long as the module is installed on the target. 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.

Is the dump encrypted?

It can be. The dump is compressed on your own server, and if you turn on optional AES-256 encryption it is encrypted there too and goes to your storage encrypted. The passphrase is known only to you: it lives in the module's (or WordPress plugin's) settings, and in the panel you enter the same passphrase only for verification; we do not store it and cannot open your backups. If you lose it, encrypted backups cannot be recovered. Encrypted archives are opened with the Yedekalma module or the WordPress plugin; with encryption off, the dump is a standard SQL file. Either way, backup files are not stored on our servers.

How do I know my backup actually works?

Once a backup is taken, the file's integrity is verified with a checksum and the dump is checked to confirm it completed in full. Backups go through 8-layer verification (coverage, content, database, trend, presence at destination, integrity, drill, incremental chain), and a weekly sample restore test downloads an archive on your server and checks its integrity and the completeness of the database dump. The Backup Report Card shows the databases on the site next to those in the backup and flags any that are missing — so a 'there's a backup, but it's empty' situation doesn't slip through silently.

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