Understand full and incremental WordPress backups

Tell full and incremental WordPress backups apart, understand their dependency chain, and learn why a later valid run may become full again.

Last reviewed

A full backup writes all selected database and file content. An incremental can reuse unchanged rows from earlier stored volumes and writes only changed data, so it depends on the backups it references.

Four panels show comparing completed rows, separating new bytes from restore size, preserving the referenced chain, and reading the dependent-backup deletion refusal.
Four panels show comparing completed rows, separating new bytes from restore size, preserving the referenced chain, and reading the dependent-backup deletion refusal. Open full-size screenshot.

Steps

  1. Open dosya Backup → Backups and compare the Type, Contents, Size, and Stored columns for two completed runs.
  2. Read an incremental row’s contents hint, such as incremental, 38 MB new. The main size is the restore set; the hint is the newly written portion.
  3. Expect the first connected backup to be full. Database-only runs, local-only runs, and runs without a usable previous remote manifest also stay full.
  4. For an incremental, the plug-in must still see the prior backup and every referenced backup as uploaded or verified, find their local volumes, and keep the base full younger than 30 days.
  5. If Dosya cannot list earlier backups, the new row records dosya could not be reached to check the earlier backups, so this backup is a full one. A chain that exceeds the reference ceiling also restarts full.
  6. Before deleting any base, check the action refusal. The list disables deletion and states how many newer backups depend on that row; delete dependents first only when you intend to remove the chain.

Backup scope and backup kind are different. Database, Files, and Database + files describe contents; full or incremental describes whether stored volumes reuse earlier data.

Reference for “Understand full and incremental WordPress backups”: Dosya WordPress plug-in overview page.
Reference for “Understand full and incremental WordPress backups”: Dosya WordPress plug-in overview page. Open full-size screenshot.

Expected result

Each row identifies its effective backup kind and newly stored bytes. A full fallback remains a valid independent backup; an incremental remains restorable only while its referenced local and remote chain is retained.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.