Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #54654
    Greg Simpson

    Here is the scenario:
    I have backed up a site that I wanted to move to another server. The original server has a version of mysql 5.6 and 5.7. We used the 5.7 version. This connection in the wp-config.php file shows the following:
    /** MySQL hostname */
    define(‘DB_HOST’, ‘localhost:/var/lib/mysql/mysql57.sock’);
    This is and always has worked just fine. Now I want to restore the site to another server, yet this server only has version 5.7.
    When I try to restore this, I get an error saying that it cannot establish a DB connection. It has restored the old wp-config.php including the sock file that does not exist on the new server. What I would like to know is:
    Can I exclude that file from a restore? And are there any others that are gotcha’s that you know about?


    Brandon C

    Hi Greg,

    Thanks so much for reaching out and thanks for using Total Upkeep backups and migrations plugin.

    I know these restoration issues can be frustrating, but we’ll be happy to help.

    The first thing to check on is the restoration logs for the failed attempts. Navigate to Total Upkeep > Tools > Logs and look for the log with a filename similar to restore-XXXXXXXX.log and a timestamp corresponding to the restoration that failed.

    If you can paste that log here, we’ll be able to determine what’s causing the failure.

    You can also try restoring your backup using Total Upkeep’s command line utility.

    We look forward to assisting you further with this!


    I’ve uploaded a Zip file to my CPanel and am trying to restore it. The Zip file was downloaded from another website using Total Upkeep/Boldgrid Backup.

    This is the message I get.

    “Total Upkeep – Restoration failed

    Incompatible Archive.: PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature”

    Brandon C

    Hi Hannelore,

    Generally speaking, the PCLZIP_ERR_BAD_FORMAT error means that the backup archive was somehow corrupt.

    We might be able to determine what went wrong based on the archive log on your main site. Navigate to Total Upkeep > Tools > Logs and look for the log file with a name like archive-XXXXX.log and the timestamp corresponding to when you took the backup.

    We’re looking for the last few lines of that log, where you should see a message like Backup complete! or else find some evidence of errors that happened during the backup process. If you can paste those log entries here, we can investigate further and get you all fixed.

Viewing 4 posts - 1 through 4 (of 4 total)
  • The topic ‘Receiving an error when attempting to restore a website with Total Upkeep’ is closed to new replies.