Snapshot not running

The Snapshot is not running and doesn't show any Error messages. No JS errors, no errors in debug.log. Small file like .htacces and wp-config.php can be backed up. But it is not working for other larger files

  • James Morris

    Hello T. Webb,

    I hope you are well today. I'll be following up with you regarding your chat.

    Unfortunately, I was not able to login to your website using the details provided in chat. In order to help you better with your issue, would you please grant me access to your site and server?

    Please visit the Contact page and complete the form with the following information:

    Subject: "Attn: James Morris"

    In the Message box, please provide the following:

    - link back to this thread for reference
    - any other relevant urls

    - Admin login:
    Admin username
    Admin password
    Login url

    - Hosting Control Panel Login
    Admin username
    Admin password
    Login url


    - FTP credentials
    (and port if required)

    Best regards,

    James Morris

  • James Morris

    Hello T. Webb,

    I've been digging into your Snapshot issue and I'm finding a number of things that could be causing the failure.

    First, your PHP configuration wasn't really optimal given the large amount of files you have. I've added a .user.ini file with the following directives:

    max_execution_time = 600
    memory_limit = 1024M
    upload_max_filesize = 512M
    post_max_size = 512M

    I also updated your wp-config.php as follows to enable WordPress to make use of the extra memory:
    define( 'WP_MEMORY_LIMIT', '1024M' );

    I found that the Snapshots were still failing, so I performed some deeper investigation. I found that you have a high number of Zip files that are very large.

    511M ./wp-snapshots/tmp/20170927_[url_deleted]
    1.6M ./wp-snapshots/tmp/20170927_[url_deleted]
    16K ./php.ini.txt(10).zip
    44M ./wp-content/themes/
    68M ./wp-content/themes/
    24M ./wp-content/themes/
    150M ./wp-content/updraft/
    4.0K ./wp-content/updraft/
    336K ./wp-content/updraft/
    33M ./wp-content/updraft/
    160M ./wp-content/updraft/
    20K ./wp-content/uploads/2016/04/[url_deleted]
    8.0M ./wp-content/uploads/2016/03/
    108M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    156M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    696K ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    46M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    71M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    52M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    149M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    46M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    46M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    47M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    612K ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    51M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    51M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    133M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    149M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    149M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    71M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    51M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    154M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    149M ./wp-content/uploads/backupbuddy_backups/backup-[urL_deleted]
    8.0K ./wp-content/uploads/snapshot/
    498M ./wp-content/uploads/snapshot/_backup/1501178332/
    1.4M ./wp-content/uploads/snapshot/_backup/1501178332/
    1.2G ./wp-content/uploads/snapshot/_backup/1501031312/
    1.4M ./wp-content/uploads/snapshot/_backup/1501031312/
    72M ./wp-content/uploads/snapshot/_backup/1506807691/
    27M ./wp-content/uploads/snapshot/_backup/55465f5f/
    88M ./wp-content/uploads/snapshot/_backup/55465f5f/
    498M ./wp-content/uploads/snapshot/_backup/55465f5f/
    40M ./wp-content/uploads/snapshot/_backup/55465f5f/
    99M ./wp-content/uploads/snapshot/_backup/55465f5f/
    109M ./wp-content/uploads/snapshot/_backup/55465f5f/
    134M ./wp-content/uploads/snapshot/_backup/55465f5f/
    188M ./wp-content/uploads/snapshot/_backup/55465f5f/

    Such files can cause issues with Snapshot. So, I added some global exclusions.


    This still did not work, so I continued to dig in further. It seems you hare hitting your I/O cap which is causing the Snapshot process to be terminated.

    You're also dangerously close to reaching your Disk Space Limit. Both issues could cause Snapshot to fail due to the temp files that Snapshot has to write.

    My suggestion at this point would be to do a thorough house cleaning on the site and remove any files you no longer need, especially large files. Once the site is cleaned up, please try running Snapshot again. Your configuration is now set to give Snapshot everything it could need to run right.

    If it still does not work, please contact your hosting provider and ask them if they can increase your I/O cap.

    Please let us know if this resolves your problem.

    Best regards,

    James Morris

  • Lindeni Mahlalela

    HelloT. Webb

    I hope you are doing great today.

    I have also looked at this issue and it seems my colleague James has already pointed out that the server is hitting the I/O Usage limit when running Snapshot. I/O limits the number of read/write operations on the disk and Snapshot uses this to scan files and create an archive.

    If this I/O usage is reached, the server may return a "404 not found" or "500 Internal Server Error" depending on your host's configuration. We had a similar issue before on Namecheap and GoDaddy, in both cases I asked the member's to contact the host and here is a quote from one of the responses from Namecheap:

    In simple words, your shared hosting package does not provide enough resources to perform such operations.

    Here are the similar threads:

    Go Daddy:

    It seems you are suffering the same kind of limit with Namecheap and as they admitted, you will need to upgrade your hosting account to one with a much higher I/O limit or find host that does not have such limits.

    I am sorry there is nothing we can do on our side with regards to hosting limit and I hope your host can help you out with this. You can reach out to them and refer them to this ticket so the understand what you are talking about. We will always be happy to help in any way possible, so just update us about what they said.

    Have a nice day.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.