This backup troubleshooting guide is for site owners, freelancers, and agency teams whose WordPress backup failed after setup. Use it when you see backup errors, a backup that stops halfway, or no new backup in days. Skip it if you have no backup issues and your backups restore cleanly. Over 10+ years of managing WordPress sites, I have seen the same few causes repeat. My team has built W3SpeedX backup screens for 14 months, since September 2025. This article is part of our WordPress backup guide series.
Key Takeaways
- Most failures have a small set of causes. Schedules, timeouts, memory, space, and access cover nearly all of them.
- Read the error first. The message points to the cause.
- Test with a manual backup. A manual run separates schedule problems from resource problems.
- A finished backup is not a good backup. Restore it to prove it.
- Watch for missed runs. Silent failures hurt most.
What Does "WordPress Backup Not Working" Mean?
A WordPress backup not working can mean four different things. Each one calls for a different fix. The backup may fail to start. It may start and stop before it finishes. It may finish but produce a damaged or incomplete archive. Or it may finish well, yet fail to restore.
Each symptom has different causes. A backup that does not start points to scheduling. A backup that stops halfway points to limits on time, memory, or space. A damaged archive points to interrupted transfers or storage trouble. A failed restore points to a mismatch between the archive and the target site.
Naming the symptom first saves hours when you work through backup errors. According to the WordPress developer documentation, a complete backup holds both the database and the files. If either half is missing, the backup fails the one test that matters. Keep that standard in mind as you troubleshoot.
Common Backup Errors and Their Causes at a Glance
Symptom |
Common cause |
First fix |
|
Backup does not start |
Schedule not firing, low traffic |
Run a manual backup, check the scheduler |
|
Backup stops partway |
PHP timeout |
Raise the time limit, exclude large folders |
|
Fatal memory error |
Memory limit too low |
Raise the memory limit |
|
Backup ends with no file |
Disk or quota full |
Free space, move copies offsite |
|
Upload to storage fails |
Expired credentials, blocked connection |
Reconnect storage, check firewall |
|
Archive will not open |
Interrupted transfer |
Re-run and verify size |
|
Restore fails |
Incomplete archive or version mismatch |
Try an earlier restore point |
Step Zero: Read the Backup Error and Check the Date
Start with two facts. First, read the exact error message. Second, check the date of the last successful backup. These two facts narrow the search more than any other step.
A message about "maximum execution time" points to a timeout. A message about "allowed memory size" points to memory. A message about "no space left" points to disk or quota. A message about permissions points to file access. Copy the message into your notes before you change anything.
Then check the last successful date. If the last good backup is 2 days old and your schedule is daily, you have missed 2 runs. That tells you the problem began 2 days ago. Look at what changed then, such as a plugin update, a host change, or a traffic drop. In my experience, a recent change explains most sudden failures.
Why a WordPress Backup Failed: 12 Common Causes
The next 12 sections cover why a WordPress backup failed in real sites. Each one names the symptom, explains the cause, and gives a fix. Work through them in order, because the early causes are the most common.
Cause 1: The Schedule Does Not Fire
A backup that does not start is often a scheduling problem. It is one of the most common reasons a WordPress backup failed. Many backup plugins rely on WP-Cron, the WordPress task scheduler. According to the WordPress developer documentation on WP-Cron, WP-Cron checks its task list on every page load. It does not run constantly the way a system scheduler does.
This has a direct effect on quiet sites. The documentation warns of a task due at 2:00 PM when no page loads until 5:00 PM. A site with little traffic may skip its backup window for hours. This means a low-traffic site can miss a nightly backup, because nobody visited at the right moment.
The fix has three parts. First, run a manual backup to confirm that the backup process itself works. Second, check whether WP-Cron is disabled in wp-config.php, since some hosts turn it off. Third, for exact timing, ask your host to run a system cron job on a fixed interval.
A cloud service that schedules backups outside your site avoids this dependency on page loads. Check how your tool triggers runs before you trust a schedule.
Cause 2: The PHP Time Limit Stops the Backup
A backup that stops halfway often hits the PHP time limit. According to the PHP manual, scripts have 30 seconds by default. If the limit is reached, the script returns a fatal error. Your host may set a different value in php.ini.
Backups take time because they read many files and a large database. A small site finishes in seconds. A site with a large media library or a big database may need minutes. When the script exceeds the limit, PHP kills it, and you get a partial archive or no archive.
Here is the fix path. First, ask your host to raise max_execution_time for backup jobs, often to 300 seconds or more. Second, exclude folders you do not need, such as cache directories and old backup folders. Third, use incremental backups, which store only what changed. An incremental run touches fewer files, so it finishes sooner.
Shared hosting often caps these values. If your host refuses to raise them, move to a backup method that does the heavy work off your server.
Cause 3: The Memory Limit Is Too Low
A fatal error mentioning "allowed memory size exhausted" points to memory. According to Hosting.com's knowledge base, WordPress sets the PHP memory limit to 40 MB by default. That means one PHP script can use up to 40 MB of RAM.
Backups can need more. Building a large archive in memory pushes past a low limit, and the process dies. Plugins that load many libraries add to the load.
The fix is to raise the limit. In wp-config.php, define WP_MEMORY_LIMIT as 64 MB or 128 MB, and WP_MAX_MEMORY_LIMIT as 256 MB for admin tasks. Then check the new values under Tools, Site Health, Info, in the WordPress dashboard. Hosts may override your setting, so confirm the change took effect. If the error continues, ask the host for a higher server-level limit.
Cause 4: The Disk or Quota Is Full
Backups need space. When the server disk or your hosting quota is full, the archive cannot finish. The process may end with no error at all, which makes this cause easy to miss.
Local backups pile up. Each full copy of a 2 GB site takes 2 GB. Fourteen copies take 28 GB. Many shared plans allow far less than that, so old backups quietly consume the quota.
Many backup issues start here. Fix it in two steps. First, check disk usage in your hosting panel and delete old archives you no longer need. Second, move backups offsite so they stop consuming host space. Our backup storage guide explains the options. Also set a retention rule, such as keeping 7 daily, 4 weekly, and 3 monthly copies.
Cause 5: The Database Is Large or Locked
Large databases slow backups down. Tables full of old revisions, transients, spam comments, or logs grow fast. A backup that once took 20 seconds can take 5 minutes after a year of buildup.
A busy site adds another problem. A backup reads the database while visitors write to it. That can cause long locks or inconsistent copies. If the process waits too long, it times out.
The fix starts with cleanup. Delete old post revisions, expired transients, and spam. Optimize tables, then compare the size before and after. Next, schedule backups for quiet hours so the load is lighter. For very busy stores, a faster schedule with incremental copies gives smaller, more frequent snapshots.
Cause 6: Security Tools or Firewalls Block the Backup
Security plugins and firewalls can block backup requests. A web application firewall may treat a backup tool's connection as suspicious. A security plugin may block the files a backup needs to read, or the ports it uses to upload.
These backup errors show up as the same failed step each time. You often see a connection or "forbidden" message. It may work when you pause the security tool. That test tells you where to look.
The fix is to allowlist the backup tool. Add its IP addresses or user agent to your firewall rules, and exclude backup paths from aggressive scanning. Do not disable your security tool entirely. Instead, narrow the rule that blocks the backup. According to Patchstack's 2025 mid-year report, 6,700 new vulnerabilities were identified in the WordPress ecosystem in six months. Security tools matter, so adjust them rather than remove them.
Cause 7: File Permissions and Ownership
A backup tool must read every file it archives. When files have the wrong permissions or belong to a different user, the tool cannot read them. Some backups skip those files silently, and others stop with an error.
This often follows a migration or a manual upload by FTP. Files uploaded as one user may be unreadable by the web server. Folders created by a plugin may carry restrictive permissions.
Check the error log for "permission denied" lines. Then correct ownership and permissions through your host panel or SSH. Typical safe values are 755 for folders and 644 for files, though your host may advise otherwise. After the fix, run a manual backup and compare the file count with the previous good run.
Cause 8: Storage Destination Problems
Many backups run well but fail at the upload step. The destination may have expired credentials, a revoked token, a full bucket, or a changed password. The local archive exists, yet the copy does not reach the cloud.
This failure is dangerous because the backup process looks healthy. You may see "backup complete" while the offsite copy is missing. That means you believe you have an offsite copy when you do not.
Reconnect the storage account and re-authorize any tokens. Check free space at the destination. Then confirm the newest file really appears in the storage location. Do not trust the success message alone. Our backup security guide covers how to protect those credentials.
Cause 9: Plugin and Theme Conflicts
Backup plugins can conflict with other plugins. Caching plugins, optimization plugins, and other backup tools sometimes interfere. Two backup plugins running at the same time can fight for resources and lock files.
An update can trigger a new conflict. A backup that worked for months may fail the day after a plugin update. This is why the last successful date matters in step zero.
Test by deactivating other plugins one at a time, or by using a staging site. Run a manual backup after each change. When the backup works, you have found the conflict. Then contact the plugin author, or choose a different combination. Avoid testing on a live site when a clone is available. See Site Cloning and Restore for a safer way to test.
Cause 10: Excluded or Oversized Files
Large files cause trouble. A single 2 GB video can stall an archive. Old backup folders inside the WordPress directory get backed up again and again, making each new archive larger.
Exclusion rules help. Exclude cache folders, temporary files, and previous backups. Keep the rules narrow so you do not exclude something you need. In W3SpeedX, exclude patterns let you skip folders and keep backups lean.
Review the rules every few months, because other backup issues often trace back to old rules. Rules that were safe a year ago may hide new, important folders now.
Cause 11: Corrupt or Incomplete Archives
Sometimes a backup finishes but the file is damaged. An interrupted upload, a full disk at the last moment, or a dropped connection can leave a truncated archive. The size looks smaller than usual, or the file will not open.
Check the size and date of every new backup against the previous one. A sudden drop in size is a warning sign. Try opening the archive or listing its contents. Then restore it to a staging site to confirm.
If an archive is damaged, delete it and re-run the backup. Do not keep a bad file as your only copy. Keep earlier restore points until a new one passes a test.
Cause 12: Restore Failures
A backup that cannot restore is the worst case. Common causes include incomplete archives and missing database tables. Different PHP or WordPress versions also break restores, as does a target with too little space.
Work through it in order. First, try an earlier restore point, since the newest copy may be the damaged one. Second, restore files and database separately, and see which half fails. Third, download the ZIP and restore by hand with a database tool and FTP.
In W3SpeedX, a restore includes the database by default through the Include DB checkbox. Progress runs from 0 to 100 percent, and a restore cannot be undone, so take a manual backup first. Our WordPress backup recovery guide covers the full restore process.
A Simple Backup Troubleshooting Process
Use the same backup troubleshooting process every time. It saves time and prevents guesses.
- Record the symptom. Note whether the backup failed to start, stopped, or failed to restore.
- Read the error. Copy the exact message.
- Check the last good date. Find when the problem began.
- Look at recent changes. Updates, host changes, and traffic drops matter.
- Run a manual backup. This separates scheduling from resource problems.
- Fix one thing at a time. Change one setting, then test.
- Verify with a restore. Prove the fix on a staging site.
Changing many settings at once hides the real cause. In my experience, patience here saves more time than any single tweak.
How to Check That a Backup Really Worked
A success message is not proof. Verify every important backup with four checks. Check the date, so you know it is current. Check the size, so you know it is not truncated. Check the contents, so you know both files and database are present. Then restore it to a staging site.
The restore is the test that counts. Time it, and note anything missing. A tested backup gives you confidence, and a timed restore gives you a real recovery time. Our backup checklist shows how to prepare before major changes.
How to Prevent Backup Issues
Prevention beats repair. Choose a schedule that matches how often your site changes. Our backup frequency guide explains how. Store copies offsite so a host problem cannot take them. Keep several restore points so one bad file does not leave you stranded.
Automate the routine so nobody has to remember it. Our backup automation guide covers this. Then add monitoring, because automation still fails quietly. According to NAKIVO's ransomware backup guidance, you should alert on changes to backup configuration. Alerts catch tampering and mistakes early.
Review the whole setup every 3 months. Check that every site has a schedule, that offsite copies exist, and that a recent restore passed. A review of 15 minutes catches most problems before they become failures.
Backup Troubleshooting With W3SpeedX
W3SpeedX stores backups in cloud storage, away from your host. Several features help you spot problems early. Key features include:
- Status view. The dashboard shows last backup, next backup, and storage used for each site.
- Run tracker. A tracker records backup and restore runs.
- Backup Now. You run a manual backup to test, and it creates a restore point labelled manual.
- Restore points. Each is labelled manual or scheduled, so you can pick a clean copy.
- Exclude patterns. You skip cache and temporary folders to keep archives lean.
- ZIP downloads. You download a whole backup, or single files and folders, to restore by hand.
- Incremental backups. A run stores only what changed.
Six schedules are available: Monthly, Weekly, Daily, Every 12 hours, Hourly, and Realtime. Monthly is free. Weekly costs 1 USD per site, Daily 2 USD, Every 12 hours 3 USD, and Hourly 5 USD. Realtime is billed at the Hourly rate. See the WordPress Backup Service and Pricing pages. Pair backups with Website Uptime Monitoring to learn quickly when a site fails.
Case Study: How We Built Backup Visibility
We built the backup schedule settings in September 2025. We added the Every 12 hours and Realtime options on 30 January 2026, 4 months in. We found that pricing needed fixes, in February 2026 and again in April 2026. We found that owners needed to see what ran and when. On 4 September 2026, we added a tracker for backup and restore runs.
In practice, a backup problem is easiest to fix when you can see it. The result was a dashboard that shows last backup, next backup, and storage used for every site. We have revised the backup screens 102 times over 14 months. It turned out that owners ask about failed runs far more often than about features. Visibility turned troubleshooting from guesswork into a short check.
A Quick Backup Troubleshooting Review
Run a short review whenever a backup fails, and again every 3 months.
Start with the symptom. Decide whether the backup failed to start, stopped, produced a bad file, or failed to restore. Then check the common causes in order: schedule, time limit, memory, space, access, and storage. Next, run a manual backup and watch it finish. A manual success tells you the process works and points to scheduling or limits.
Finish with a restore on a staging site. Record how long it took. If the restore works, the problem is solved. If it does not, try an earlier restore point and repeat. Keep notes of what you changed, so the next failure takes minutes instead of hours.
Related Guides on Backup Problems
This article covers failures. For the wider picture, read our guides on backup strategy, backup best practices, backup methods, and disaster recovery. Together they cover planning, storage, security, and recovery.
Conclusion
A WordPress backup not working is rarely a mystery. Missed schedules, timeouts, low memory, full disks, and blocked connections explain most failures. Good backup troubleshooting follows one order. Check the last backup time, read the error, fix the cause, and run a manual backup to prove it. Then test a restore, because only a restored copy counts.
Check your latest backup date today. If it is older than your schedule allows, start with the steps above. To see last backup, next backup, and storage used for many sites, see the WordPress Backup Service. For the full background, read the WordPress backup guide.
Frequently Asked Questions
Why is my WordPress backup not working?
Common causes are missed schedules, PHP timeouts, memory limits, full disks, blocked connections, and expired storage credentials. Check the error log first.
Why did my WordPress backup fail?
A backup fails when the process stops before it finishes. Timeouts, low memory, and no free space are the usual reasons.
How do I fix a backup that does not start?
Check that the schedule is active. WP-Cron runs only on page loads, so a quiet site can miss runs. Trigger a manual backup to test.
What does a PHP timeout have to do with backups?
PHP stops scripts after 30 seconds by default. A large site can exceed that limit, so the backup ends with a fatal error.
How much memory does a WordPress backup need?
WordPress sets a default limit of 40 MB. Large sites need more, so raise WP_MEMORY_LIMIT to 128 MB or higher.
Can a full disk break backups?
Yes. If the server or storage destination has no free space, the archive cannot finish. Free space or move copies offsite.
How do I know a backup is complete?
Check the size, date, and contents, then restore it to a staging site. Only a restore proves completeness.
What should I do if my restore fails?
Try an earlier restore point. Then restore files and database separately, or download the ZIP and restore by hand.
How can I find out when a backup fails?
Watch the last backup time and set alerts for failed runs. A missed run is the first warning sign.
How does W3SpeedX show backup problems?
The dashboard shows last backup, next backup, and storage used. A tracker records backup and restore runs.
Does W3SpeedX offer a manual backup for testing?
Yes. Backup Now runs an on-demand backup and creates a restore point labelled manual.
How often should I test my backups?
Test a restore every 3 months, and after any hosting or plugin change.


