BugWP logo BugWP
Back to Community
Home / Community / General

Troubleshooting Common WPvivid Restore Errors: From Memory Limits to Corrupted Files

39 threads Sep 9, 2025

Content

Struggling with a Failed WPvivid Restore? You're Not Alone.

Many users of the 'Migration, Backup, Staging – WPvivid Backup & Migration' plugin encounter issues during the restore process, especially when migrating a site. The errors can be cryptic, leaving you unsure of what went wrong. Based on community reports and troubleshooting logs, this guide covers the most common restore failures and their solutions.

Common WPvivid Restore Errors and Their Fixes

1. Memory Exhaustion Errors

Error Example: Allowed memory size of 268435456 bytes exhausted

Why it happens: Restoring a large website, especially one with a big database, can require more PHP memory than your server currently allows.

Solution: Increase the PHP memory limit on your server. You can often do this by editing your wp-config.php file and adding this line:

define('WP_MEMORY_LIMIT', '512M');

If that doesn't work, you may need to contact your hosting provider to increase the limit server-wide.

2. Corrupted or Incomplete Backup Files (PCLZIP Errors)

Error Examples:

  • PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature
  • PCLZIP_ERR_BAD_FORMAT (-10) : Invalid archive structure
  • A file uploads but doesn't appear in the restore list.

Why it happens: This is one of the most frequent issues. The backup archive (.zip file) did not complete downloading or uploading correctly, becoming corrupted. This can happen due to an unstable internet connection, server timeouts, or insufficient disk space during the backup creation or upload process.

Solution:

  1. Verify the Backup File: Before uploading, try to extract the backup zip file on your local computer. If it fails, the backup is corrupted and you will need to create a new one from the source site.
  2. Manual Upload Method: Instead of using the plugin's uploader, use FTP or your hosting provider's file manager (e.g., cPanel) to upload the backup files directly to the /wp-content/wpvividbackups/ directory on the target site. Then, click the "Scan uploaded backups" button in the WPvivid plugin.
  3. Check Disk Space: Ensure the target server has enough free disk space—at least twice the size of the backup file.

3. Timeout and Stuck Restore Processes

Error Example: The restore process hangs indefinitely at a certain percentage (e.g., 83%) without a clear error, or you see a generic "time out error."

Why it happens: Server configuration limits, such as max execution time for PHP scripts, can stop the restore process before it finishes, particularly on large sites.

Solution:

  1. Increase the max_execution_time in your PHP settings, either via php.ini or by adding set_time_limit(300); to a relevant file (consult your hosting provider for the best method).
  2. Try restoring components individually. If you have a full backup split into parts (database, plugins, themes, uploads), restore them one by one instead of all at once. This puts less strain on the server per operation.

4. File Permission Issues

Error Example: WPVIVID_PCLZIP_ERR_WRITE_OPEN_FAIL (-1) : Unable to open temporary file

Why it happens: The web server (e.g., www-data) does not have write permissions in the wpvividbackups directory or other WordPress folders it needs to extract files to.

Solution: Use an FTP client or file manager to check the permissions on the /wp-content/wpvividbackups/ directory. They should typically be set to 755 for folders and 644 for files. Your web server user must have read and write access.

5. Apparent Success But No Change

Error Example: The restore reports "success" but the website looks unchanged.

Why it happens: This usually indicates that the database was not restored, often because the backup did not include it. The restore process only successfully extracted files like themes and plugins.

Solution: Always ensure you are using a "Full Backup" that includes both files and the database. Check the backup details on the source site before migrating.

General Best Practices for a Smooth Restore

  • Free Up Resources: Before starting, ensure your target server has ample disk space and memory.
  • Check the Logs: WPvivid creates detailed logs. Always check them for specific error messages, as they are the best clue for diagnosing problems.
  • Test on a Staging Site: If possible, test the migration process on a staging environment first to identify potential issues before affecting your live site.

By methodically working through these common causes, you can resolve most restore issues encountered with the WPvivid plugin.

Related Support Threads Support