⚡ Only What Changed 🗄 Table-Level Database ✉️ Email by UID 🧠 Smart Skip ⚡ Only What Changed 🗄 Table-Level Database ✉️ Email by UID 🧠 Smart Skip
Incremental Backup

Stop Copying Everything Every Time
Back Up Only What Changed

Back up a 10 GB site once a day in full and you move 300 GB a month — while the part that actually changed is usually a few hundred megabytes. Optional incremental backup transfers only the difference: runs get shorter, your server works less, and your storage fills far more slowly. A fresh full backup is still taken at set intervals.

No credit card required · free trial until the end of the year

Component by Component

Where Incremental Applies

Many solutions work incrementally on files only. In Yedekalma, incremental mode covers files, database and email in the PHP Backup Module, and files only in the WordPress plugin. In the chunked mode used for very large sites, only email is incremental.

📁

Files

Files that changed (by modification time) and newly added files are transferred; deletions are marked in the chain.

🗄

Database — table level

Each table's checksum is compared and only changed tables are dumped.

✉️

Email — by UID

Each message is tracked by its IMAP UID, so only new arrivals are downloaded.

🧠

Smart skip

If nothing changed at all, no empty backup is produced — the skip is recorded instead.

🔗

Chain management

Every part links to the last full backup (differential); a fresh full backup is taken periodically.

✅

Integrity checks

Every part's checksum is checked, and one layer of the 8-layer verification looks at the incremental chain. Corruption does not build up silently.

What You Gain

The Payoff

⏱

Shorter runs

Because only the changed part is processed, backups take less time and your server is busy for a shorter period.

📉

Less storage

The same retention takes far less space, lowering your own cloud costs.

🔁

More frequent backups

Because each run is lighter, taking hourly instead of daily backups becomes easier on your server.

💰

A price discount

A discount applies to each component where incremental is on — see current prices.

Honestly: what does incremental cost you?

Incremental backup is not a free win. Its price is that restores depend on a chain: returning to a point in time requires the last full backup plus that point's incremental part.

We limit that risk two ways. Chains do not grow — every incremental part links directly to the last full backup (differential), and a fresh full backup is taken periodically; backups you start manually are always full. And every part is checksum-verified, so corruption does not build up unnoticed. Even so, taking an occasional full backup of critical data remains a good habit.

FAQ

Incremental Backup — Frequently Asked Questions

Instead of copying everything each time, incremental backup transfers only the data that changed since the previous backup. Runs are shorter, server load is lower and storage fills far more slowly. At Yedekalma every incremental is taken relative to the last full backup (differential), so a restore combines that full backup with the part you pick.
No. A restore is a single operation in the wizard; the system determines which full backup and which incremental parts are needed and applies them. From your side there is no difference between restoring from a full backup and from an incremental chain.
Yes, in the PHP Backup Module, at table level. Each table's checksum is compared and only changed tables are dumped. If your orders table changes hourly while your settings table has been static for months, only the changed part is transferred. In the WordPress plugin and in the chunked mode used for very large sites, the database is not incremental — each run takes a full dump.
Yes, in the PHP Backup Module (including its chunked mode for very large sites). Each message is tracked by its IMAP UID and only messages received since the last backup are downloaded, which drastically shortens runs for mailboxes with tens of thousands of messages. In the WordPress plugin, email is not backed up incrementally.
No empty backup is produced. If no change is detected the backup is skipped and the skip is recorded, so your storage does not fill with pointless files. We call this smart skip.
That is the known weakness, and it is addressed in two ways. Chains do not grow: every incremental links directly to the last full backup (differential), and a fresh full backup is taken periodically; backups you start manually are always full. And every backup's integrity is checksum-verified, so corruption does not accumulate silently.
Yes. A discount applies to every component where you turn on the "back up only what changed" option. You can see current prices live on the pricing page.

Back Up More Often and Spend Less

Run backups more frequently while taking up less space. Free until the end of the year.

Create Free Account

Backup verification →