0

We currently have a physical db server on premise, running mySql version 5.6. We have another instance set up on an Azure virtual machine, as we are in the process of migrating our data center to Azure.

We don't have a dedicated DBA, and we are following the steps in this tutorial from the mySql site:

https://dev.mysql.com/doc/refman/5.7/en/replication-howto-additionalslaves.html

We keep failing on the 2nd step of copying the data directory, is there a workaround for this, or a better way to go about replicating?

1

Copying data directory would work if you are using the same version of MySQL. As per you question, you are copying from 5.6 to 5.7, so this way wouldn't work.

Now: you mentioned you are "migrating", and the steps you are following are for "creating new slave"!

If you want to "migrate", a better way is the following:

  1. Make a full backup using mysqldump, or other "logical" backup tools (as opposed to physical copy of the files)
  2. restore this backup on your destination server

HTH

  • While we are migrating, we have all of our servers (the ones already migrated to the cloud and the physical ones) pointing at our physical mysql server. We have been trying to run the azure instance as a slave, so that we can cut over and make that the primary. Our difficulties have been in getting it to update to the point where it is in sync with the physical server. – JohnP Sep 16 '16 at 1:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.