Backup or Migration gets to 32% then stalls

  • Resolved bethgee

    (@bethgee)


    2 years, 8 months ago

    Hello,

    I have seen others have had the same issue as me – when I try to back up or migrate my clients site, it processes to 32% and then stalls and doesn’t progress any further!

    I tried – 

    In General Settings,
Uncheck the option “Merge all backups into a single package”
Uncheck the option “Calculate the size of files before backup”
Save Changes
In Advanced Settings,
Check ‘Enable optimization mode for web hosting/shared hosting’
Compress Files Every 100Mb
PHP script execution timeout for backup 900s
PHP memory limit for backup 512MB
Retrying 9 times
Saved changes. Then run a backup again.

If the problem still persists, please also change the following settings in the php.ini file of the server(please contact the web host if you are not the server manager),
Change the PHP max execution time to at least 900s
Change the PHP memory limit to at least 512Mb

    It doesn’t impact the issue.

    I have found a bunch of topics about this but they all end with your asking for the error log to be sent and then no more responses after that about how to resolve the issue!

    Please help!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter bethgee

    (@bethgee)

    I also keep getting a pop up that says

    ‘wpvivid_request: error(Internal Server Error): an error occurred when trying to establish communication with your server. This error may be request not reaching or server not responding. Please try again later.’

    Help please!!

    Plugin Support tonyrobins

    (@tonyrobins)

    Hi @bethgee

    Can you please also check whether the web sever is a Litespeed server? As on a Litespeed server, in order to optimize the network, the server will kill requests that exceed a certain time, for example, 30s. Here is a doc where we showed how to check it.

    If so, you can add the following rules to the .htaccess file of the website to prevent Litespeed timeout.

    <IfModule LiteSpeed>
    RewriteEngine On
    RewriteRule .* - [E=noabort:1, E=noconntimeout:1]
</IfModule>

    All the best,

    Thread Starter bethgee

    (@bethgee)

    Not LiteSpeed server, its Linux

    Thread Starter bethgee

    (@bethgee)

    Ah, actually, I am wrong, it is litespeed!

    Where in the .htaccess file should I add the above code??

    Thread Starter bethgee

    (@bethgee)

    I added that code and tried to do the backup again…

    Now I get a popup error

    ‘wpvivid_request: error(Not Found): an error occurred when trying to establish communication with your server. This error may be request not reaching or server not responding. Please try again later.’

    and also an on page error

    ‘Error:Calculating the size of files, folder and database timed out. If you continue to receive this error, please go to the plugin settings, uncheck ‘Calculate the size of files, folder and database before backing up’, save changes, then try again.’

    Plugin Support tonyrobins

    (@tonyrobins)

    Hi @bethgee

    You can add the rule under the line ‘END WordPress’ in the .htaccess file.

    For the error ‘Error:Calculating the size of files, folder and database timed out.’, please go to WPvivid Settings, in General Settings, uncheck the option ‘Calculate the size of files before backup’, save changes.

    For the error ‘wpvivid_request: error(Not Found)’, can you please send us a debug zip(you can download it from WPvivid plugin’s Debug tab of the site) to contact(at)wpvivid.com to help troubleshoot the issue?

    Thanks,

    All the best,

    Thread Starter bethgee

    (@bethgee)

    Have sent through the plugin.

    Is now showing a

    ‘Backup failed, it seems due to insufficient server resource or hitting server limit., Please switch to Website Info page to send us the debug information. ‘

    Error…..

    Plugin Support tonyrobins

    (@tonyrobins)

    I am also posting the troubleshooting result here so users who may have the same issue can see this:

    The backup failure is due to insufficient server resources. The backup task times out after 120 seconds.

    It is recommended to contact the web host and increase the max_execution_time to 300 seconds at least. Then run a backup again.

    Additionally, if possible, please also increase the web server disk I/O because the archiving speed is slow in the backup progress.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Backup or Migration gets to 32% then stalls’ is closed to new replies.