Site migration unsuccessful

UpdraftPlus Home › Forums › Paid support forum – UpdraftPlus backup plugin › Site migration unsuccessful

Tagged: 

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • December 11, 2017 at 3:36 am #248616
    priscilla
    Participant

    Hello,

    I’ve used UpdraftPlus to migrate websites in the past without problem. However, there seems to be a problem in migrating a dev site to production this time. I’d be happy to attach the error Log File but the UI doesn’t seem to support this. Please help!

    Thanks in advance.

    Priscilla.

    December 11, 2017 at 3:38 am #248617
    priscilla
    Participant
    This reply has been marked as private.
    December 11, 2017 at 6:32 am #248629
    Bryle Crodua
    Moderator

    Hi Priscilla,

    The backup log shows the file transfer connection is being cut off unexpectedly by the receiving server. The backup is able to resume, but it is possible that the interruption to the transfer is causing the corruption.

    In this case, you will need to use one of the alternative transfer methods to migrate the Uploads to your new site. These can be found in Step 3 of the migration guide:

    How do I migrate to a new site location?

    I would also recommend asking you hosts/server admin for the new location to investigate why the connection is being cut off. The relevant error is:
    0532.159 (1) ERROR (Exception): remotesend: backup_2017-12-10-1758_TerraCana_Dev_82054a600662-db.gz: Failed to upload file: cURL error 52: Empty reply from server (http_request_failed) (code: 0, line: 63, file: /home/prisuufy/terracana.priscillathen.com/wp-content/plugins/updraftplus/methods/remotesend.php)

    Kind Regards,
    Bryle

    December 11, 2017 at 8:51 am #248644
    priscilla
    Participant

    Thank you for the quick response, Bryle! I saw that some of the files it was trying to upload was almost 500MB so the enormous size could be why. I deleted a bunch of the big files as they mostly backups of backups, and Updraft successfully backed up the dev site.

    Then I successfully uploaded all the zipped folders except to the new (production) site. All the folders were uploaded except the first content folder, which probably is due to the file permissions that need to be changed, as I’m getting the message:

    “Upload error (code -200) : HTTP Error. Error:
    The file failed to upload. Please check the following:
    – Any settings in your .htaccess or web.config file that affects the maximum upload or post size.
    – The available memory on the server.
    Further information may be found in the browser JavaScript console, and the server PHP error logs.”

    The new site is hosted with Godaddy, and the hosting plan is so simplified (non-technical) that I cannot actually specify any values (ex. 775).

    When I try to restore the backup, I get the message:
    “The database server that this WordPress site is running on doesn’t support the collation (utf8mb4_unicode_520_ci) used in the database which you are trying to import. You can choose another suitable collation instead and continue with the restoration (at your own risk).”

    Which uni-code setting should I pick? (We’re in Canada but are fine using American English).

    Also, what would happen if a multi-archive backup set has a missing folder (in this case the first Uploads folder)? Would it just be pictures missing?

    December 12, 2017 at 6:47 pm #248966
    Dee Nutbourne
    Moderator

    Hi,

    For the upload error, I would recommend uploading the remaining backup file to the server via FTP or your hosting control panel filemanager.
    Upload the file(s) to the ‘wp-content/updraft’ directory.

    If the Uploads backup is missing a file, a number of images (or other uploaded files) will be missing.

    The database collation issue is due to the new database being an older MySQL version than the original server, which does not support ‘utf8mb4’ collations
    If possible, I would recommend asking your hosts to update the MySQL server to a more current version.

    If not, you will need to change the collation from ‘utf8mb4_unicode_520_ci’ to ‘utf8_unocode_520’.

    Best Wishes,
    David N

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • The topic ‘Site migration unsuccessful’ is closed to new replies.