BugWP logo BugWP
Back to Community
Home / Community / General

Troubleshooting WPvivid Backup Stuck or Failing: Common Causes and Solutions

31 threads Sep 10, 2025

Content

Experiencing a backup that gets stuck at a certain percentage, fails with a cryptic error, or times out is one of the most common frustrations when using the 'Migration, Backup, Staging – WPvivid Backup & Migration' plugin. Based on extensive community reports, these issues are almost always related to server resource limits and configuration, not a fundamental flaw in the plugin itself.

This guide will walk you through the most effective troubleshooting steps to resolve these stubborn backup problems.

Why Do Backups Get Stuck or Fail?

The backup process is resource-intensive. It requires your server to execute PHP scripts for a long time, use a significant amount of memory (RAM), and perform heavy read/write operations on your disk. If your web hosting environment has limits on any of these resources, the backup process can halt, time out, or fail completely. Common sticking points are 13%, 28%, 32%, 42%, 64%, and 80%, often indicating where the process of backing up specific large files or database tables begins.

Step-by-Step Troubleshooting Guide

Follow these steps in order. After each step, try running a new manual backup to see if the issue is resolved.

Step 1: Optimize WPvivid Plugin Settings

The first and most effective place to start is within the plugin's own settings, which are designed to work within restrictive hosting environments.

In General Settings:

  • Uncheck 'Merge all the backup files into a single package when a backup completes'. Creating multiple smaller files is less demanding than one large one.
  • Uncheck 'Calculate the size of files before backup'. This pre-scan can itself time out on large sites.

In Advanced Settings:

  • Check 'Enable optimization mode for web hosting/shared hosting'. This mode is specifically for resource-limited environments.
  • Set 'Compress files every' to a lower value, such as 100 MB or even 50 MB. This breaks the backup into smaller chunks.
  • Set 'PHP script execution timeout for backup' to a high value, such as 300 or 900 seconds.
  • Set 'PHP memory for backup' to 512M.
  • Increase 'Retrying times when encountering a time-out error' to 3 or more.
  • Use 'Exclude the files which are larger than' to skip very large files (e.g., 100MB) that are likely to cause timeouts.

Remember to Save Changes after adjusting these settings.

Step 2: Check and Increase Server Resources (If Possible)

The plugin can only work with what the server provides. If you have access to your server's configuration (e.g., via cPanel, or by contacting your host), check these key settings:

  • PHP max_execution_time: Set to at least 300 seconds.
  • PHP memory_limit: Set to at least 512MB.
  • PHP Extensions: Ensure the zlib extension is installed and enabled, as it is required for compression.

On some hosts, especially shared hosting, these values may be hard-limited, and upgrading your hosting plan may be the only solution.

Step 3: Understand and Act on Warning Messages

You may see a warning like: 'The database might be too large... may run out of server memory...'

This is not an error but a warning. It means the plugin has detected your site is large relative to common server limits. You can safely click OK to proceed with the backup. The warning is simply making you aware of a potential point of failure.

Step 4: Investigate Download and I/O Issues

If your backup completes but you cannot download it, or the backup process causes high I/O usage that crashes your server, the issue is likely a server-level download or process limit.

  • Try downloading the backup file via a file manager plugin or your hosting control panel's file manager. If it also fails, the limit is definitely on the server side.
  • For I/O issues, the optimization settings in Step 1 are your best mitigation, but the ultimate fix may require a hosting plan with higher resource allowances.

When All Else Fails: Get Specific Help

If you have tried all the steps above and your backup still fails, the next step is to gather specific information about your environment. The 'Migration, Backup, Staging – WPvivid Backup & Migration' plugin has a Debug tab that can generate a log file. This file contains detailed technical information about your server configuration and the exact point where the backup failed, which is essential for further diagnosis.

By methodically working through these server and plugin settings, you can significantly increase the success rate of your backups and overcome the most common hurdles faced in shared hosting environments.

Related Support Threads Support