Issues migrating between 2 sites with xcloner

  • Resolved stemcelltechnologies

    (@stemcelltechnologies)


    7 years, 5 months ago

    I am trying to use xcloner to migrate data between test sites via AWS S3 bucket and only having partial success.

    site1.example.com
    WP install: /var/www/html/wordpress

    site2.example.com
    WP install: /var/www/html

    These are AWS hosted test sites and have their own individual RDS databases.

    1) Installed xcloner plugin and enabled S3 bucket connectivity on both sites
    2) Generate full backup (excluding wp-config.php) on site 1 and upload to S3 bucket
    [wp-config.php is excluded as these sites are created using Cloudformation templates meaning the wp-config.php file is dynamically generated including the DB connection and SALT values etc so you don’t want to overwrite it]
    3) Download backup from S3 bucket to site2 locally
    4) Proceed with “Only wp-content” restore to target path /var/www/html
    5) It appears to be complete – “Done restoring backup-2017-10-25_23-28-793e3.tgz.” appears above the files processed log. The available buttons are showing as < RESTORE and SKIP NEXT >
    6) RESTORE re-runs the restore by the looks of it and SKIP NEXT moves on to the next section “Target Mysql Details”
    7) I can set the source and target URL, however the “Please Select the target database backup file to restore” drop down box is empty with nothing to select…

    What have I missed?

    If I download and extract the .tgz archive I can find a “database-backup.sql” inside the /xcloner-6f96a/ folder so it appears to be there.

    If I go back and run the Database only restore, it seems to work and the box is populated as expected. However when I run the find and replace step for source:site1 target:site2 it works for about 30-60 seconds then displays “Lost connection with the API, please try and authentificate again”

    After this the site appears to be dead, all pages just load blank white with no content.

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

  • 7) restore db is empty because you’ve only restore the wp-content folder, you need to do a separate db restore for that data. Please note, if you’ve done the mysql restore on your live site database, it could be that you’ve overwritten your login session, i advise to always restore to a separate database from the live one.

    Hope it helps

    Thread Starter stemcelltechnologies

    (@stemcelltechnologies)

    Thanks for the quick reply!

    I suspected that may be the case unfortunately… I’m looking for a simple click to restore option so perhaps this plugin isn’t going to work for us.

    This is not a live site but the database is technically in use as I’m logged into the WordPress site to perform the restore.

    This is a test environment that can be spun up from a template in ~15 mins. Once up the plan was to simply install a plugin, connect to the S3 bucket, pull down the backup and restore it. Having to manually restore the database outside of WordPress or to a 2nd database then switch it is a bunch of extra effort I’m looking to avoid.

    Compared to some other plugins though your scheduled backups to S3 works perfectly and is one of the better ones I’ve used.

    In case you did not notice, you can restore your site without the need to install wordpress on your new host, you have the option to upload only the xcloner restore script to your new host and supply it’s url on your original machine restore screen, it will use it as an end api point to transfer and restore data. You will need to supply the mysql details to a new db however, but this will help with your existing db issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Issues migrating between 2 sites with xcloner’ is closed to new replies.