• Hi

    I have just upgraded WP to WP 3.8 and upgraded to the lateat version of your plugin 2.65.

    I really love having a DB interface in WP. However the issue is with the backups.

    I have 2 WP sites, same version, same plugins on the same VS.

    One site is working correctly e.g after 10 backups it deletes the oldest and overwrites it with the next backup as it should ( a rolling backup system ).

    However on my other system it just seems to have stopped at 10 (latest is in January 27, 2013 @ 7:38 pm – 87.1 MiB.

    Both sites have the same setup, 10 backups on a weekly schedule. Also optimise, repair are scheduled.

    However on the working site it shows me the “Next backup date: December 22, 2013 @ 8:06 pm” as well as the next Repair / Optimize dates.

    However on the other site they just say “NA” next to each date e.g

    Next backup date: N/A
    Automatic Optimizing Of DB: Next optimize date: N/A
    Automatic Repairing Of DB: Next repair date: N/A

    I have just upgraded your plugin, but I do this regularly anyway.

    I have also deleted one old backup so there is 9 backup files and 1 spare slot.

    I have also just done a manual backup and that worked without a problem.

    The .htaccess file is in the write place and the backup folder has permissions to save to the folder as I can see the new file in it.

    I can code in PHP/MySQL so if you have any hints to what I can do to work out what has gone wrong or why there is no scheduled dates for the next backup/repair/optimize etc then please point me in the right direction as I can debug it myself.

    Thanks for any help you can give me.

    http://wordpress.org/plugins/wp-dbmanager/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Lester Chan

    (@gamerz)

    Try a Cron Plugin like http://wordpress.org/plugins/wp-crontrol/ to see if the cron is scheduled?

    When you save the settings of DBManager, it is still N/A?

    Thread Starter strictly-software

    (@strictly-software)

    Both sites are on the same server.

    There is no info on the path or URL I need to supply for the CRON job to initiate the backups in any WP DB settings that I can see.

    In my own plugins if I need a CRON job setup I will always say on the config page something like (from Strictly System Check) this…

    To run this report you will need to setup either a CRON job on your server or if you don’t have access to your server you can easily setup a WebCron job using one of the many free services available on the web.

    Cron Command

    */20 * * * * /usr/bin/curl http://www.mysite.com/wp-content/plugins/strictly-system-check/strictly-system-check-reporter.php?code=2edeewe5911x___2a

    WebCron Ready URL

    http://www.mysite.com/wp-content/plugins/strictly-system-check/strictly-system-check-reporter.php?code=2edeewe5911x___2a

    And I find which program they have installed (WGET, CURL, LYNX etc) to use so I can show the correct path for a copy n paste.

    However I see no mention of a cron job needing to be set here. So I am guessing the plugin SHOULD be setting an internal WP Cron job to be initiated by a page loading.

    However for performance reasons – on both sites (same VS server) I have disabled the standard WP CRON URL that gets fired on every HTTP request (overkill) and instead setup a manual one that runs every 5 minutes instead.

    So for both sites I have this set up in my CRON jobs on my server and the times are set for every 5 minutes. As I don’t schedule posts or need WP to do its own jobs ALL the time as I have access to my server I just run it every 5 mins to run what WP needs e.g

    wget -U StrictlyCron -q -O – http://www.mysite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

    I installed that WP Control plugin on both sites.

    The site that isn’t working shows a number of records but this is the only one that has a “delete” next to the end of it.

    twicedaily 43200 (12 hours) Twice Daily Delete

    However on the site that is working the same record is the only one with the delete next to it. However there are more options and it includes

    dbmanager_optimize 172800 (2 days) WP-DBManager Optimize Schedule
    dbmanager_backup 259200 (3 days) WP-DBManager Backup Schedule
    dbmanager_repair 432000 (5 days) WP-DBManager Repair Schedule
    jetpack_weekly 604800 (1 week) Jetpack weekly

    Both sites use JetPack.

    Whenever I save the settings I just get NA.

    I don’t know why the CRON is not being setup when I use the manage interface though. No error messages are returned which would be helpful to say why a cron job wasn’t setup.

    I guess I need to manually set these up if the plugin can’t for some reason add the records to the database?

    Thread Starter strictly-software

    (@strictly-software)

    Quick update.

    As I tried to add the cron jobs manually, either WP DB Backup or Jetpack the message at the top of the screen says “Successfully added the cron schedule jetpack_weekly” BUT there is nothing in the table.

    If I refresh the page or login / logout nothing happens.

    It’s as if something is PREVENTING me from adding these cron jobs.

    It would be helpful if some kind of error message was displayed – there is nothing in the error log file.

    Plugin Author Lester Chan

    (@gamerz)

    “There is no info on the path or URL I need to supply for the CRON job to initiate the backups in any WP DB settings that I can see.” — That is not needed, WP will does a pseudo cronjob

    “So I am guessing the plugin SHOULD be setting an internal WP Cron job to be initiated by a page loading” — Correct, as I was saying above.

    Your case is tricky because it is not just WP-DBmanager not working? Jetpack as well? How about trying to post it in the JetPack support, you might get answers as I think more people look at the forums then this.

    Thread Starter strictly-software

    (@strictly-software)

    Hi

    I seem to have managed to get Jetpack working, it was due to disabling the plugin (in the usual disable all then re-enable to find the cause) and not “re-connecting” to a WP account which Jetpack requires.

    There are bugs in JetPack which I have already posted to them about however the issue with this plugin is that I am using it across two sites on the same virtutal server.

    Both have Jetpack on. Both have exactly the same plugins installed.

    An automatic DB update was carried out on the site I was having issues with JetPack with last night however the other site which hasn’t given me problems with Jetpack (maybe because the themes differ?) hasn’t done an automatic DB update.

    I can manually create an update from within admin on this site but when I change the settings I get NA for the “next scheduled time” and using that WP Cron job I cannot
    a) see any cron jobs for the DB plugin.
    b) OR actually create any manually.

    Therefore I am wondering if you could give me the SQL to actually run an update/insert statement into wp_options to actually create the necessary cron job records? This way I can force the CRON records to exist.

    Thanks

    Plugin Author Lester Chan

    (@gamerz)

    “Therefore I am wondering if you could give me the SQL to actually run an update/insert statement into wp_options to actually create the necessary cron job records? This way I can force the CRON records to exist.” — Unfortunately I can’t because that is via WP, on my plugin side, I am using just an API. So I am not too sure how does the API translate to an SQL query on WP end.

    Thread Starter strictly-software

    (@strictly-software)

    Hi

    Well I have tried disabling JetPack and that doesn’t seem to work.

    It has actually caused me a nightmare today as I didn’t have any recent backups and I found a crashed and unrepairable wp_postmeta table so I have lost all the data in that due to not being able to restore a recent backup.

    There has to be a way for me to find out why when I set a schedule for 2day backups and hit save that it doesn’t actually do anything and comes back with N/A?

    Some debug code I could put in a file somewhere maybe to find out what the problem is?

    Any help would be great.

    Thanks

    Plugin Author Lester Chan

    (@gamerz)

    Have you thought of out the box to use a cron job with myqsqldump to backup the db directly rather than using it via plugin?

    Thread Starter strictly-software

    (@strictly-software)

    Yes that is what I am having to do now, use VMIN to do backups however I just don’t get why the plugin works on one DB on the same server (same plugins – versions etc) and not on this one.

    Surely you must know what the code is doing that sets the time for the next schedule?

    Where does it get the current timestamp from
    and
    What maths does it use to add to that to get the next backup date
    and
    What has to run/load/fire to initiate the backup process

    As I am getting N/A when I save the times for backups and the error message “nothing selected” there must be some issue with one of the dates somewhere OR the setting of the wp_option to create the next date for the backup?

    Any SQL or PHP I can use (just tell me and I will write it myself) and I can throw it into the page you tell me so I can see what is NOT happening that should be happening.

    Seems strange it works on one DB and not the other when they are both the same size (in posts/pages, tags/categories, users) and have the same settings for permalinks and so on.

    Any help to debug would be good.

    Plugin Author Lester Chan

    (@gamerz)

    Unfortueny I can’t answer these questions:
    1. Where does it get the current timestamp from
    2. What maths does it use to add to that to get the next backup date
    3. What has to run/load/fire to initiate the backup process

    because all this are part of WP inner workings and I have to really dig in (which I can’t due to time constraint).

    Maybe Googling will get you more help than from me, https://www.google.com/search?q=wp-cron+debug

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Automatic Backup stops at the number without deleting old files’ is closed to new replies.