Moving problem relating to GoDaddy

  • Resolved amancalledhawk

    (@amancalledhawk)


    9 years, 10 months ago

    Ok people….here is a weird problem someone out there may have an answer to. We are using a synology NAS to host our wordpress server. Basically, it had a nervous breakdown during our last upgrade. In a rush to get things back up and running, we discovered problems with our backup and had to recreate our site using Godaddy as a host (don’t ask them any questions, turns out most of them have no idea how their system works). Now that our WP server is back up again, we have been trying to back up/restore and/or clone our running site back onto our side. What was supposed to be a simple task has turned horribly wrong. After 8 hrs bashing the keyboard, we have given up talking to Godaddy (their people hide their insults when they talk to clients….just not overly well).

    We think we have found the culprit…and want to pose it to the forum. During one of the imports, data was accidentally imported into the same DB. When it was reviewed, it was observed that Godaddy was using MyISAM and Synology was using innoDB.

    It seems that there are a few questions to be answered.

    1. Would this be the reason the imports are failing?
    2. Is there a simple way of importing knowing there are 2 different storage engines? or
    3. Will one of the DB have to be changed to allow for the import?

    Two days have been wasted reading about similar solutions with no success. Help is requested in moving the site, and then some ideas are needed on how to backup a site so this doesn’t repeat itself.

    Thank you…

Viewing 4 replies - 1 through 4 (of 4 total)

  • data was accidentally imported into the same DB

    Drop this database and reimport from backup, it will for sure support both innodb and MyIsam.

    if needed you can convert innodb to myisam too.

    Thread Starter amancalledhawk

    (@amancalledhawk)

    Drop this database and reimport from backup

    That was not a question….it was a given. But thanks.

    it will for sure support both innodb and MyIsam.

    I know it will support both, but that again is not the question. All of my imports are failing, not just this one. So the question again is, could the fact that sinology uses innoDB and GoDaddy uses MyISAM be the problem? I had the impression that innoDB was backward compatible, but this doesn’t seem to be the case here.

    if needed you can convert innodb to myisam too.

    innoDB is the evolution of MyISAM. I know that MyISAM is stable, but Synology uses innoDB. If anything, I would have to convert from MyISAM to innoDB. But will this actually be required, and can it be done safely?

    Thread Starter amancalledhawk

    (@amancalledhawk)

    If someone has a simple way of moving the website, or knows of an app or plugin that will work, let me know. At the end of the day, I need working solutions. I would love to avoid spending more days recreating a working web site, again. Once done, I need something that will keep a good backup in case this happens again.

    Thread Starter amancalledhawk

    (@amancalledhawk)

    Merry Christmas

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Moving problem relating to GoDaddy’ is closed to new replies.

Tags