Verify a completed WordPress backup
Confirm a WordPress backup completed locally, distinguish uploaded from remotely verified, and run an optional local volume integrity check.
Last reviewed
A completed archive, a successful upload, and remote verification are three distinct states. Use the row’s action availability and storage badge first, then use WP-CLI when you need to validate the local volume bytes.

Steps
- Open dosya Backup → Backups and locate the row by created time, note, type, and contents. A failed row has no Restore or Download action and is not a completed backup.
- Confirm its local receipt: a normal completed row lists size and volume downloads and offers Restore. local means the copy exists only on this WordPress server.
- Read the remote badge. dosya · uploading is unfinished; dosya · not verified means upload completion was accepted but Dosya has not confirmed every volume; dosya · verified is the remote verification receipt.
- If command-line access is available, run
wp dosya listto copy the exact backup ID, then runwp dosya verify <backup-id>. This reads every local volume and checks its SHA-256 and archive structure. - Treat N volumes verified. as local integrity evidence only. Volume N is missing or damaged. names the first local volume that fails; it does not change the remote badge.
- For recovery confidence, keep the row and its dependencies, and perform a controlled restore test on a disposable installation. Verification does not prove the restored application behaves correctly.
Remote completion validates up to 2,000 volumes and 2,000 references, checks that files are live and in the correct folders, checks sizes, and accepts references only to uploaded or verified backups from the same site.

Expected result
The backup has a usable completed local row, a clearly identified remote state, and—when WP-CLI was run—a local volume-integrity receipt. You know whether the copy is local-only, uploaded but awaiting verification, or remotely verified.
Related guides
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.