Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WPvivid Backup Not Working: Causes and How to Fix It

WPvivid Backup Not Working: Causes and How to Fix It

Short answer

WPvivid backups usually fail because the server runs out of PHP time or memory, WP-Cron does not fire scheduled backups, disk space runs out, or the remote upload breaks. Read the latest log, lower the archive size, raise server limits and reconnect remote storage.

Key takeaways

  • The WPvivid log usually names the exact cause.
  • Timeouts and memory limits are the most common failure.
  • Scheduled backups depend on WP-Cron firing.
  • Backups need free disk space and a writable folder.
  • Reconnect remote storage if uploads fail.
  • Test a restore to prove a backup works.

Why is WPvivid Backup not working?

WPvivid backups usually fail because the server runs out of time or memory, scheduled tasks do not fire, the backup folder is not writable, or the upload to remote storage breaks partway.

WPvivid Backup is a free plugin that backs up, restores and migrates WordPress sites. Most of the time it works without fuss, but large sites and limited hosting can push it past its limits.

Typical symptoms include a progress bar stuck at a percentage, a failed message, scheduled backups that never run, or backups that finish locally but never reach Google Drive or Dropbox.

This guide covers each cause in order. For background on the plugin, see our explainer on what WPvivid does.

What are the common WPvivid problems at a glance?

Most WPvivid failures fit one of a few patterns, and matching your symptom to a cause saves time.

SymptomLikely causeFirst fix
Stuck at a percentagePHP timeout or memory limitLower compression size, raise limits
Scheduled backups never runWP-Cron not firingSet up a real cron job
Error writing filesFolder permissions or disk spaceFree space, check permissions
Local backup works, upload failsRemote storage auth or size limitsReconnect storage, smaller chunks
Fails on very large sitesHuge media or log filesExclude unneeded folders
Fails after plugin updateConflict or stale settingsCheck for conflicts, update all

Start with the row closest to your problem.

How do you read the WPvivid log?

Open the WPvivid Backup menu in WordPress, go to the log area, and open the latest backup log, where the last lines usually show the exact error or the stage where the backup stopped.

Logs turn guesswork into a clear answer. Look for the final lines before the failure.

Common clues include:

  • A message about maximum execution time.
  • A message about allowed memory size.
  • A message about failing to open or write a file.
  • An error code returned by Google Drive, Dropbox or another storage service.

WPvivid's own backup failed troubleshooting page maps common log messages to fixes. Keep the log open while you work through the steps below.

Is the server running out of time or memory?

Large backups need a lot of PHP time and memory, so if the log mentions a timeout or memory limit, lower WPvivid's compression size and raise the server limits.

Hosting plans set a maximum execution time for PHP scripts and a memory limit. When compressing a big folder takes longer or uses more memory than allowed, the process is killed.

WPvivid's advanced settings include options for archive size, script timeout and memory used during backup. The exact labels change between versions, so look for these ideas:

  1. Split or compress size: smaller archive parts mean each step finishes faster.
  2. Script execution timeout: give each step more time if the host allows it.
  3. Memory limit for backup: raise it within what your host permits.

You can also raise limits at server level. Our guides on increasing PHP memory limit explains the memory side.

For timeouts, see our guide to increasing max execution time.

The PHP manual on max_execution_time explains what the limit controls. Shared hosts often cap these values, so ask support if changes do not take effect.

Are scheduled backups failing to run?

WPvivid schedules rely on WP-Cron, which only fires when someone visits your site, so quiet sites or sites with WP-Cron disabled can miss backups entirely.

If manual backups work but scheduled ones never appear, cron is the likely cause.

Check your wp-config file for a line that disables WP-Cron. If it is there, you must run wp-cron from a real server cron job.

The WordPress cron documentation explains how WP-Cron depends on traffic. Our guide on running WordPress cron from the server shows how to set up a reliable schedule.

You can also check whether WPvivid's events are listed and overdue with a cron viewer. See how to view WP-Cron events.

Can WPvivid write to its backup folder?

WPvivid saves backups to a folder inside wp-content before uploading them, so a full disk or a folder without write permission stops every backup.

Check your hosting disk usage first. Backups need free space roughly equal to your site size, and old local backups add up fast.

Then check the backup folder. In WPvivid settings you can see where local backups are stored. Using FTP or your host's file manager, make sure the folder exists and is writable.

Standard permissions are 755 for folders and 644 for files. Do not use 777, which is a security risk and often blocked.

Delete old local backups you no longer need, or lower the number of backups WPvivid keeps. Our guide on how to get FTP access to WordPress helps if you have not used FTP before.

Why does the upload to remote storage fail?

Remote uploads fail when the storage connection has expired, the account is full, the file is too large for one request, or the host blocks the outgoing connection.

If the backup finishes locally but never appears in Google Drive, Dropbox, OneDrive, Amazon S3 or FTP, focus on the upload stage in the log.

Try these steps:

  1. Remove and reconnect the remote storage in WPvivid settings.
  2. Check the storage account has enough free space.
  3. Lower the archive split size so each upload is smaller.
  4. Test a small manual backup sent to remote storage.
  5. Ask your host whether outgoing connections to that service are blocked.

Authorisation tokens can expire, especially after changing your Google or Dropbox password. Reconnecting fixes this.

Are large files or folders causing the failure?

Very large media libraries, log files, cache folders and other plugins' backup folders slow backups and often cause timeouts, so exclude anything you do not need.

Look through wp-content for unexpected large folders. Common culprits are:

  • Cache folders from caching plugins.
  • Old backups from another backup plugin.
  • Debug and error logs that have grown for months.
  • Large video files that are already stored elsewhere.

WPvivid lets you exclude folders and files from a backup, and in some versions set a size limit for individual files. Use these options to skip data that can be rebuilt.

Do not exclude the uploads folder entirely unless your media is backed up another way. Without it, restored posts will have broken images.

Is another plugin causing a conflict?

Security plugins, firewalls, caching plugins and other backup plugins can block WPvivid's background requests, so test with them disabled to find any conflict.

WPvivid makes repeated background requests to itself while a backup runs. A security firewall may treat those as suspicious and block them.

Steps to test:

  1. Take note of which plugins are active.
  2. Deactivate other backup plugins first.
  3. Pause security or firewall plugins briefly.
  4. Run a small manual backup.

If it works, turn plugins back on one by one. Our guide on how to fix a plugin conflict explains the method in more detail.

Server firewalls such as ModSecurity can do the same. If the log shows blocked requests, ask your host to check their firewall logs.

What if the restore fails instead of the backup?

Restore failures share many causes with backup failures, especially timeouts, memory limits and disk space, and WPvivid has a separate guide for them.

Common restore problems include a database import that stops partway, a site that loads with broken links, or a white screen after restore.

Check WPvivid's restore failed page for specific messages. Make sure the destination site has the same or newer PHP version and enough disk space.

If you are moving the site to a new domain, use the migration feature rather than a plain restore. WPvivid's migration failed guide covers that process.

How do you confirm backups work after fixing them?

Run a manual backup, check the log shows it completed, confirm the files arrived in remote storage, then test a restore on a staging site.

A finished backup is not the same as a working backup. Only a test restore proves you can recover.

Our guide on how to test a WordPress backup explains how to do this without touching your live site.

A staging site is the safest place for that test.

Keep an eye on the next few scheduled runs. If they all finish, the problem is solved.

When should you contact WPvivid support?

Contact support once you have checked limits, cron, disk space, remote storage and conflicts, and the log still shows an error you cannot explain.

WPvivid offers a way to send debug information from inside the plugin, which includes server details and logs. Use that when opening a ticket.

You can also post on the WPvivid support forum on WordPress.org. Include your WordPress, PHP and WPvivid versions, your host, and the last lines of the log.

If problems keep coming back on cheap shared hosting, consider your host's own backups as a second layer. Our comparison of cPanel backup vs plugin backup explains the trade-offs.

Frequently asked questions

Why is my WPvivid backup stuck at a percentage?

A stuck progress bar usually means a PHP process timed out or ran out of memory. Check the log for the last message, lower the archive split size in WPvivid settings, and raise PHP memory and execution time if your host allows it.

Why do WPvivid scheduled backups not run?

Schedules depend on WP-Cron, which only fires when someone visits the site. Quiet sites or sites with WP-Cron disabled can miss backups. Set up a real server cron job that calls wp-cron on a regular schedule.

Why does WPvivid not upload to Google Drive?

The storage authorisation may have expired, the account may be full, or the upload may be too large for one request. Reconnect the storage in settings, check free space, and lower the archive size so each upload is smaller.

Can a security plugin stop WPvivid backups?

Yes. WPvivid makes background requests to your own site while a backup runs, and some firewalls block them. Pause security plugins briefly to test, and ask your host to check server firewall logs if the problem continues.

How much disk space does WPvivid need?

Plan for free space at least equal to the size of your site, plus room for any older local backups you keep. Delete old local copies or lower the retention number if your hosting disk is nearly full.

Sources

  1. Backup failed WPvivid Docs
  2. Restore failed WPvivid Docs
  3. Migration failed WPvivid Docs
  4. WPvivid Backup plugin WordPress.org
  5. Cron WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.