Improper Behavior

  • Radices

    (@radices)


    9 years, 9 months ago

    Hi Lester, Thanks for this great plugin. Its the first thing I load on every new site.

    Today I noticed a behavior that could have gotten me in big trouble if I hadn’t already downloaded a copy of a backup. I keep ten copies on the server.

    The problem: When you restore a copy of the database the plugin takes a backup first and deletes the oldest one to make room. I was incrementally restoring one after the other trying to debug an issue when the GOOD one was deleted. I hadn’t noticed up until then what was happening.

    I think it would be a lot better to make it an option to not backup before a restore to avoid this from happeneing.

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

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

    (@gamerz)

    9 years, 9 months ago

    The backup is done via cron on a schedule basis, from the plugin point of view, it will not know whether a restore has been done before the backup

    Thread Starter Radices

    (@radices)

    9 years, 9 months ago

    So your saying the CRON runs every time a Restore is selected? How is this on a scheduled basis?

    Plugin Author Lester Chan

    (@gamerz)

    9 years, 9 months ago

    “When you restore a copy of the database the plugin takes a backup first and deletes the oldest one to make room”

    No it doesn’t do that, it will only run the restore command. The backup is done of a CRON bases specified in your settings. The backup and restore are both separate processes. It is run independently

    Thread Starter Radices

    (@radices)

    9 years, 9 months ago

    Hi Lester,

    Yes it does do that. That’s what I’m saying. I have it set to do one backup a day but it did one every time I did a restore.

    1 epic_dartmouth.sql.gz July 30, 2014 @ 10:53 am 14.1 MiB
    2 epic_dartmouth.sql.gz July 29, 2014 @ 3:24 pm 13.9 MiB
    3 epic_dartmouth.sql.gz July 29, 2014 @ 3:16 pm 13.8 MiB
    4 epic_dartmouth.sql.gz July 29, 2014 @ 3:15 pm 13.3 MiB
    5 epic_dartmouth.sql.gz July 29, 2014 @ 2:33 pm 13.2 MiB
    6 epic_dartmouth.sql.gz July 29, 2014 @ 2:26 pm 13.3 MiB
    7 epic_dartmouth.sql.gz July 29, 2014 @ 2:17 pm 13.9 MiB
    8 epic_dartmouth.sql.gz July 29, 2014 @ 2:08 pm 13.7 MiB
    9 epic_dartmouth.sql.gz July 29, 2014 @ 2:08 pm 13.1 MiB
    10 epic_dartmouth.sql.gz July 29, 2014 @ 2:04 pm 13.5 MiB
    11 epic_dartmouth.sql.gz July 29, 2014 @ 2:04 pm 12.9 MiB

    Plugin Author Lester Chan

    (@gamerz)

    9 years, 9 months ago

    I can’t reproduce this problem on my end.

    I did a restore of the DB and it doesn’t create a new backup. I also double check the code, it doesn’t even trigger the backup code when you click restore.

    I set my “Automatic Backing Up Of DB” to a week on my test site.

    Take a look at the screenshot http://i.imgur.com/hcxQPwg.jpg

    Today is 31st and the last backup date is 30th even after restoring.

    Thread Starter Radices

    (@radices)

    9 years, 9 months ago

    I’ll try it on another site and report back. Mine are all set to daily.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Improper Behavior’ is closed to new replies.