⚡ 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. Incremental backup transfers only the difference: runs finish faster, your server works less, and your storage fills far more slowly.

🎁 Start Free — 14 Days See Pricing

No credit card required · 14-day free trial

All Three Components

Where Incremental Applies

Most solutions do this for files only. Yedekalma applies it across all three components.

📁

Files

Changed and newly added files are transferred; deletions are recorded 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

Chains do not grow forever; a fresh full backup periodically starts a new one.

✅

Integrity checks

Every part is checksum-verified so corruption does not accumulate unnoticed.

What You Gain

The Payoff

⏱

Shorter runs

Backups can finish in seconds instead of minutes, so your server is busy briefly.

📉

Less storage

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

🔁

More frequent backups

Because it is cheaper, hourly instead of daily becomes realistic.

💰

A price discount

With incremental enabled a discount applies to the relevant components — see pricing.

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 full backup plus the parts that followed it.

We limit that risk two ways. Chains do not grow indefinitely — a fresh full backup periodically starts a new chain. 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. In exchange, restoring requires combining the parts of a chain.
No. A restore is a single operation; 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, 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.
Yes. 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.
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 forever — a fresh full backup periodically starts a new chain. And every backup's integrity is checksum-verified, so corruption does not accumulate silently.

Back Up More Often and Spend Less

Run backups more frequently while taking up less space. 14 days free.

Create Free Account

Backup verification →