How many WordPress backups should you keep?

Why yesterday’s backup may not be enough

Not every problem is noticed on the day it happens. A missing page, damaged image or unwanted change may sit quietly until someone needs it. If you keep only the newest backup, you may discover that the copy you saved already contains the problem.

Older recovery points give you choices. They do not guarantee a clean website or a successful restore, but they can help you find a version from before a known change. Keep notes for major releases or incidents so the dates mean something when you return to the backup list.

Start with a modest, written policy

For a small site, a policy might keep seven daily recovery points and four weekly checkpoints. Treat that as an example to discuss, not a universal minimum. A busy store, a site with large media uploads and a rarely edited portfolio can need quite different arrangements.

Describe the policy in plain language: what is kept, where it lives, who checks it and who can approve deletion. Confirm that your backup plan or plugin edition can actually implement the pattern. A retention number may mean complete sets, individual job results or a provider-specific rotation rule.

• Keep recent copies for everyday mistakes.
• Keep selected older checkpoints for problems discovered later.
• Set aside a known pre-change copy when needed.
• Review the policy when site activity or storage use changes.

Do not delete pieces of a backup set

Some tools divide a backup into several archives. Others create a full copy followed by smaller files containing later changes. A small file is not automatically useless, and an older component may be required to restore a later point.

Use the backup tool’s own retention controls where possible. Before removing files manually, check the provider’s instructions and identify the complete set. If you cannot tell which pieces belong together, stop and ask support. Freeing space is not a good trade if it leaves the remaining backups unusable.

Make space without removing your safety margin

When storage is nearly full, first confirm that a recent job completed and that you have another usable copy in a separate location. Review clearly redundant test exports or duplicate downloads before reducing the policy that protects your live website.

Choose named files or sets, record what you plan to remove and retain the newest verified set plus the recovery points you still need. Moving a file to Trash may not release the storage allowance until Trash is emptied. Check the provider’s behaviour before assuming the cleanup solved the space problem.

Keep access and privacy in the plan

A second folder in the same account is not the same as a separately accessible copy. Consider what would happen if the hosting account were unavailable or its sign-in stopped working. Check that the person responsible for recovery can reach another appropriate location.

Backups can also contain customer information that no longer appears on the live site. Keep them private and limit access. Choose retention with your business and privacy obligations in mind rather than storing everything forever. Longer retention has costs as well as benefits.

Where BackupTool fits

BackupTool keeps job reports and optional archive observations separate from your storage policy. Its evidence history is not a collection of backup archives, and retaining a report does not retain the file it describes. Manage archive retention in your backup and storage tools.