Wasted my time!

  • MisterR

    (@mister_r)


    7 years, 5 months ago

    The main question: Why does it change the table prefix but doesn’t do it correctly?

    In my case the prefix was changed to “1479285878_“.

    I had to migrate the database to another host. Since I hadn’t access to c-panel, I decided to install a plugin to grab the db. Unfortunately I chose this one. I made a backup, downloaded it and imported into the db on another host. I truly believed that the table prefix was correct.

    I had spent almost one hour before I understood that there had to be a default prefix “wp_”.

    Another plugin did a correct! db backup and I imported it successfully. The whole process took less than 5 minutes!

    • This topic was modified 7 years, 5 months ago by MisterR.
Viewing 1 replies (of 1 total)
  • Plugin Author Chris Simmons

    (@cssimmon)

    7 years, 5 months ago

    MisterR,
    We use a unique backup prefix because there are a number of updates performed on the imported database just prior to bringing it online. Examples are customers migrating their site to a new domain or changing the table prefix. All of these type updates are performed on the tables with the unique prefix and then when all updates have been completed successfully, we rename the tables. If any of these steps cannot be performed then WPBackItUp will leave the original database as is. We know this causes some challenges for customers that want to perform manual restores but we decided that we would err on the side of safety.

    Sorry it caused you difficulties, next time reach out to support. We are always available for questions and happy to help.

    chris

Viewing 1 replies (of 1 total)
  • The topic ‘Wasted my time!’ is closed to new replies.