Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for MySQL®
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
    • General questions
    • Questions about MySQL
    • Connection
    • Cluster read/write issues
    • Performance issues
    • Updating a cluster
    • Monitoring and logs
    • Migration/transfer
    • Configuring MySQL
    • All questions on one page
  1. FAQ
  2. Migration/transfer

Migration/transfer

Written by
Yandex Cloud
Updated at August 20, 2025
  • How do I transfer data to a cluster?

  • How do I move a cluster to a different folder or cloud?

  • External replication error

How do I transfer data to a cluster?How do I transfer data to a cluster?

Follow the steps described in this tutorial.

How do I move a cluster to a different folder or cloud?How do I move a cluster to a different folder or cloud?

To move a cluster:

  • To a different folder: Restore the cluster from a backup. Specify the desired folder when configuring the new cluster.
  • To a different cloud: Follow the steps in this tutorial.

External replication errorExternal replication error

Error message:

Last\_IO\_Error: 
Got fatal error 1236 from source when reading data from binary log: 
'Could not find first log file name in binary log index file'

This error may occur during external replication using the master host's specific FQDN if the master host in the source cluster has changed.

Solution:

  1. Restart replication.

  2. Run this command only once:

    STOP SLAVE;
    CHANGE MASTER TO MASTER_AUTO_POSITION = 1;
    START SLAVE;
    

If the master host in the source cluster changes, the replication will be reconfigured to use the new master host. For more information about configuration, see this MySQL® article.

Was the article helpful?

Previous
Monitoring and logs
Next
Configuring MySQL
© 2025 Direct Cursus Technology L.L.C.