Daily snapshot not created

Hello

I’I’ve configured to snapshot create a daily full backup, however, the backups are not created.

I’ve ran it manually and created new ones etc but no luck. I’m running the latest version.

What’s theissue?

  • Rupok
    • Ex Staff

    Hi Frederik,

    I’I’ve configured to snapshot create a daily full backup, however, the backups are not created

    I am so sorry for this inconvenience. Can you please tell us which backup you are trying to take daily? Regular snapshots of Managed backups?

    If regular snapshot backups, can you please go to “Dashboard > Snapshot > Settings” section and scroll down to “Error Reporting” section and put a checkmark for all three options under the “log” column and save? Please try to run it again. If it fails again, can you please send us the log? It will give us valuable insight regarding the issue.

    If you are trying to take daily managed backup, can you please go to “Dashboard > Snapshot > Managed Backups” section and on the right column, can you please check mark “Enable logging” option and select “Info” for all four options and click “Update Settings”? Please try to run scheduled backup again. If it fails again, can you please provide the logo data for that case?

    I’ve ran it manually and created new ones etc but no luck

    Can you also turn on debug mode in WordPress? To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:

    define('WP_DEBUG', true);

    In order to enable the error logging to a file on the server you need to add yet one more similar line:

    define( 'WP_DEBUG_LOG', true );

    In this case the errors will be saved to a debug.log log file inside the /wp-content/directory.

    Depending on whether you want your errors to be only logged or also displayed on the screen you should also have this line there, immediately after the line mentioned above:

    define( 'WP_DEBUG_DISPLAY', false );

    The wp-config.php is located in your WordPress root directory. It’s the same file where the database configuration settings are. You will have to access it by FTP or SFTP in order to edit it.

    Past errors here. If that file is very long, paste them to a text file and attach with your reply.

    I could tell you better about the issue if I could see it live, check your current configuration and make some tests on your site. Would you mind allowing Support Access so we can have a closer look at this?

    To enable support access you can follow this guide here:

    http://wpmudev.com/manuals/wpmu-dev-dashboard-enabling-staff-login/

    Please confirm here when you are done granting Support Access. I’m looking forward to hearing from you and resolve this issue as soon as possible.

    P.S. I’ve checked your screenshot but it seems like a bank statement to me. Can you please check the screenshot again and provide us the one which shows the error?

    Have a nice day. Cheers!

    Rupok

  • Ash
    • Code Norris

    Hello Frederick

    How busy your site is? You might notice this:

    The Snapshot scheduling process uses the WordPress Cron (WPCron) system. This is the same process used to run daily checks for updates to core, plugins and themes. It should be understood this WPCron process is not precise. If you schedule a Snapshot for a specific minute of the hour WPCron may not execute at exactly that time. WPCron relies on regular front-end traffic to your website to kickoff the processing.

    So the snapshot depends on wp cron and wp cron depends on traffic in your site. So, would you please make sure you have regular traffic in your site?

    Have a good day!

    Cheers

    Ash

  • Kasia Swiderska
    • Support nomad

    Hello Frederik,

    Have you enabled debuging in WordPress as shown by Rupok here https://wpmudev.com/forums/topic/daily-snapshot-not-created#post-1168317 ? Those are different logs than one in Snapshot. I would like to see logs from WordPress as during creation of snapshot your sites returns error “The server encountered an internal error or misconfiguration and was unable to complete your request.”.

    Also please try increasing memory limit for max_execution_time to at least 180 https://wpmudev.com/blog/increase-memory-limit/

    This also might be plugin conflict so please run a quick plugin conflict test as illustrated in getting support manual (flowchart). Let me know how it goes.

    http://wpmudev.com/manuals/using-wpmu-dev/getting-support/

    kind regards,

    Kasia