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 Restore Not Working: Causes and How to Fix It

WPvivid Restore Not Working: Causes and How to Fix It

Short answer

WPvivid restores usually fail because PHP runs out of time or memory, backup parts are missing or in the wrong folder, disk space runs out, or the database import hits a server limit. Read the restore log, raise limits, upload every part and scan again.

Key takeaways

  • The restore log usually names the failing step.
  • Timeouts and memory limits cause most stuck restores.
  • Upload every backup part and keep original file names.
  • Use FTP when backups exceed the upload limit.
  • Free at least twice the backup size in disk space.
  • Test restores on staging before you need them.

Why is WPvivid restore not working?

WPvivid restores usually fail because the server runs out of PHP time or memory, the backup files are incomplete or in the wrong folder, disk space runs out, or the database import hits a size or permission limit.

WPvivid Backup and Migration is a popular free plugin, and its restore tool normally works with one click. Problems tend to appear on large sites, cheap shared hosting, or when backups are moved between servers.

Typical symptoms include:

  • A progress bar that stops at a percentage and never finishes.
  • A restore failed message with little detail.
  • A backup that does not appear in the backup list after upload.
  • A site that loads blank or shows a critical error after the restore.

This guide works through each cause in order. If backups themselves are failing, start with our guide on WPvivid backup not working instead.

What are the common restore problems at a glance?

Most failed restores match one of a handful of patterns, so matching your symptom to a cause first saves a lot of trial and error.

SymptomLikely causeFirst fix
Stuck at a percentagePHP timeout or memory limitRaise limits, retry restore
Backup not listedFiles in wrong folder or incompleteUpload all parts, click Scan
Upload failsFile larger than upload limitUpload by FTP instead
Database step failsMax packet size or permissionsAsk host to raise MySQL limits
Site blank after restorePartial restore or PHP mismatchCheck error log, re-run restore
Login fails after restoreCache or URL mismatchClear cache, check site URL

Start with the row closest to what you see, then read the matching section below.

How do you read the WPvivid restore log?

Open the WPvivid Backup menu, go to the log area, and open the most recent restore log, because the final lines usually show the exact step and error that stopped the restore.

Logs turn guesswork into a clear answer. Look for messages that mention:

  • Maximum execution time exceeded.
  • Allowed memory size exhausted.
  • Failing to open, extract or write a file.
  • A MySQL error during the database import.

WPvivid keeps a restore failed troubleshooting page that matches common log messages to fixes. Keep the log open while you work through the steps below.

If WordPress itself shows an error, turn on debugging using our guide on enabling debug mode in WordPress, then repeat the restore.

Is the server running out of time or memory?

If the log mentions an execution time or memory limit, the restore is being cut off by PHP before it finishes, so raise those limits or ask your host to raise them for you.

A restore has to unzip archives, copy files and import the database. On large sites this can take far longer than a normal page request.

Things to try:

  • Raise the PHP memory limit. Our guide on increasing the PHP memory limit shows the common methods.
  • Raise max_execution_time in your hosting panel or php.ini file. The PHP core settings reference explains what each limit does.
  • Retry at a quiet time when the server is less busy.
  • Restore on a better host or a local environment if your plan has hard limits you cannot change.

If you see a memory error message in full, our guide on fixing allowed memory size exhausted goes deeper.

Are the backup files complete and in the right place?

WPvivid can only restore a backup it can see, so every part of the backup must be uploaded to the WPvivid backup folder before you click Scan or Restore.

WPvivid splits large backups into several zip parts. If one part is missing, the restore will fail or never start.

Check these points:

  • Download every part of the backup, not just the first file.
  • Keep the original file names. Renaming parts can stop WPvivid from recognising them.
  • Upload all parts through the WPvivid upload tool, or place them in the plugin's backup folder by FTP.
  • Use the Scan option in the backup list so WPvivid detects the uploaded files.

Also confirm the backup really finished when it was created. A backup that stopped halfway can look normal but have missing data.

Is the upload limit blocking the backup file?

If your backup archive is larger than the server's upload limit, the browser upload fails, so either raise the limit or upload the files by FTP or your hosting file manager instead.

Shared hosts often cap uploads at a modest size. Backup archives for sites with lots of media can easily exceed it.

Your options are:

  • Raise upload_max_filesize and post_max_size. See our guide to increasing max upload size in WordPress.
  • Upload the zip parts by FTP or SFTP to the WPvivid backup folder, then scan.
  • Lower the compression split size when creating future backups, so each part is smaller.

FTP uploads avoid the browser limit completely, which makes them the most reliable option for big sites.

Is there enough disk space for the restore?

A restore needs free space for the backup archive, the extracted files and the temporary data, so a nearly full hosting account often causes restores to stop partway.

As a rough guide, plan for free space of at least twice the size of your backup. Check disk usage in your hosting control panel.

To free space:

  • Delete old local backups you no longer need.
  • Remove unused themes and plugins.
  • Clear large log files and cache folders.
  • Move old media or backups to remote storage.

Once space is available, run the restore again from the start rather than resuming a broken one.

Is the database import failing?

If the log stops at the database step, the cause is usually a large table, a MySQL packet or timeout limit, a different table prefix, or a database user without full permissions.

Database problems need a closer look:

  • Large tables. Big log or session tables can time out. Clean them on the source site before backing up again.
  • Packet size. Ask your host to raise the MySQL max_allowed_packet value if errors mention packet size.
  • Permissions. The database user in wp-config.php needs rights to create, drop and alter tables.
  • Prefix mismatch. When migrating, make sure the destination site uses the same database settings WPvivid expects.

The wp-config.php documentation on developer.wordpress.org explains the database settings and table prefix.

Could a plugin or security rule be stopping the restore?

Yes, security plugins, firewalls and caching layers can block the background requests WPvivid makes during a restore, so pause them briefly and try again.

WPvivid sends repeated requests to your own site while it restores. A firewall may read that as suspicious traffic.

Try these steps:

  • Temporarily deactivate security plugins such as Wordfence while the restore runs.
  • Ask your host whether ModSecurity or a server firewall blocked the requests.
  • Turn off caching or exclude the admin area from cache.
  • Run a quick conflict test. Our guide on fixing a plugin conflict shows how.

Re-enable everything once the restore completes.

Why is the site broken after a WPvivid restore?

A blank page, critical error or login loop after a restore usually means the restore did not complete fully, PHP versions differ between servers, or old cache and URL settings are still in place.

Check in this order:

  1. Read the PHP error log to find the failing plugin or file.
  2. Confirm the PHP version matches or is close to the source server. Our guide on checking your PHP version helps.
  3. Clear every cache layer, including plugin cache, server cache and CDN.
  4. Check the site address in Settings > General or in the database options table.
  5. Re-save permalinks to rebuild rewrite rules.

If you see the critical error screen, our guide on fixing the critical error message covers recovery mode and next steps.

What if the restore still will not work?

If nothing above helps, try restoring manually by unzipping the files and importing the database, or contact WPvivid support with your restore log attached.

A manual restore is slower but avoids PHP limits:

  • Extract the WPvivid zip files on your computer.
  • Upload the WordPress files by FTP.
  • Import the SQL file through phpMyAdmin or your host's database tool.
  • Update wp-config.php with the correct database details.

For support, post on the WPvivid plugin forum on WordPress.org with your log, PHP version and backup size.

Finally, test restores regularly on a staging site. A backup is only useful if you know it restores cleanly, which is the core idea behind the 3-2-1 backup rule.

Frequently asked questions

Why is my WPvivid restore stuck at a percentage?

A stuck restore usually means a PHP process hit its time or memory limit. Read the restore log for the last message, raise memory and execution time through your host, and run the restore again from the start rather than waiting.

Why does my uploaded backup not show in WPvivid?

WPvivid needs every part of the backup in its backup folder with the original file names. Upload all parts, then use the Scan option in the backup list so the plugin detects them.

Can I restore a WPvivid backup to a different domain?

Yes. WPvivid supports migration to a new domain, and it updates URLs during the process. Make sure the destination has enough disk space and PHP limits, and clear caches after the restore.

Can I restore a WPvivid backup without the plugin?

Yes. Unzip the backup on your computer, upload the files by FTP and import the SQL file through phpMyAdmin. Then update the database details in wp-config so WordPress connects to the right database.

Should I disable Wordfence before a WPvivid restore?

If the restore fails or stops without a clear reason, pausing security plugins is a sensible test. Firewalls can block the repeated background requests WPvivid makes. Turn them back on once the restore finishes.

Sources

  1. Restore failed WPvivid Docs
  2. WPvivid Backup and Migration plugin support WordPress.org
  3. php.ini core directives PHP Manual
  4. wp-config.php 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.