ApsaraDB RDS:Migrate the data of a self-managed instance that runs MySQL 5.7 or MySQL 8.0 to an ApsaraDB RDS for MySQL instance

Identify objects that are not migrated

Run the following query on your source instance to list stored procedures and functions that you need to re-create after migration:

SELECT ROUTINE_SCHEMA, ROUTINE_NAME, ROUTINE_TYPE
FROM information_schema.routines
WHERE ROUTINE_SCHEMA NOT IN ('sys', 'information_schema', 'performance_schema', 'mysql');

Also record user accounts and time zone settings before proceeding.

Install dependencies (CentOS)

sudo yum install -y go
sudo yum install -y unzip

For Ubuntu, see Appendix 2.

Build MySQL Backup Helper

1. Download the source code:

   wget https://github.com/aliyun/mysql-backup-helper/archive/refs/heads/master.zip

2. Decompress the package:

   unzip master.zip

3. Build backup_helper:

   cd mysql-backup-helper-master
   go build -a -o backup_helper main.go

4. Build oss_stream:

   cd oss_stream
   go build -a -o oss_stream oss_stream.go

3.1 Check migration compatibility

Run backup_helper to verify that the source instance supports migration:

cd ~/mysql-backup-helper-master && ./backup_helper \
  -host <host-ip> \
  -port <port> \
  -user <username> \
  --password <password>

Replace the placeholders with your actual values:

If the check passes, proceed to the next step.

3.2 Back up and upload to OSS

Run the backup and stream it directly to your OSS bucket. Select the command for your MySQL version.

innobackupex --backup \
  --host=<host-ip> \
  --port=<port> \
  --user=<username> \
  --password=<password> \
  --stream=xbstream \
  --compress <temp-dir> | \
  ./mysql-backup-helper-master/oss_stream/oss_stream \
  -accessKeyId <AccessKey-ID> \
  -accessKeySecret <AccessKey-secret> \
  -bucketName <bucket-name> \
  -endpoint <OSS-endpoint> \
  -objectName <backup-file-name>

innobackupex --backup --host=127.0.0.1 --port=3306 --user=root --password=Aa123456@ \
  --stream=xbstream --compress /root/mysql/data | \
  ./mysql-backup-helper-master/oss_stream/oss_stream \
  -accessKeyId LTAI**************** \
  -accessKeySecret ****** \
  -bucketName test \
  -endpoint oss-ap-southeast-1.aliyuncs.com \
  -objectName backup_qp.xb

xtrabackup --backup \
  --host=<host-ip> \
  --port=<port> \
  --user=<username> \
  --password=<password> \
  --stream=xbstream \
  --compress <temp-dir> | \
  ./mysql-backup-helper-master/oss_stream/oss_stream \
  -accessKeyId <AccessKey-ID> \
  -accessKeySecret <AccessKey-secret> \
  -bucketName <bucket-name> \
  -endpoint <OSS-endpoint> \
  -objectName <backup-file-name>

xtrabackup --backup --host=127.0.0.1 --port=3306 --user=root --password=Aa123456@ \
  --stream=xbstream --compress /root/mysql/data | \
  ./mysql-backup-helper-master/oss_stream/oss_stream \
  -accessKeyId LTAI**************** \
  -accessKeySecret ******** \
  -bucketName test \
  -endpoint oss-ap-southeast-1.aliyuncs.com \
  -objectName backup_qp.xb

Replace the placeholders with your actual values:

For large databases, run the command with nohup to prevent interruptions if the session disconnects. MySQL 5.7: MySQL 8.0:

nohup sh -c 'innobackupex --backup --host=127.0.0.1 --port=3306 --user=root --password=Aa123456@ --stream=xbstream --compress /root/mysql/data | ./mysql-backup-helper-master/oss_stream/oss_stream -accessKeyId LTAI**************** -accessKeySecret ****** -bucketName test -endpoint oss-ap-southeast-1.aliyuncs.com -objectName backup_qp.xb' &

nohup sh -c 'xtrabackup --backup --host=127.0.0.1 --port=3306 --user=root --password=Aa123456@ \
  --stream=xbstream --compress /root/mysql/data | \
  ./mysql-backup-helper-master/oss_stream/oss_stream \
  -accessKeyId LTAI**************** -accessKeySecret ****** \
  -bucketName test -endpoint oss-ap-southeast-1.aliyuncs.com -objectName backup_qp.xb' &

When the backup is complete, the terminal displays completed OK !.

Log in to the OSS console to confirm the file was uploaded successfully. If the upload failed, run the backup command again.

If OSS is temporarily unavailable, save the backup to a local file first and upload later. See Appendix 3: Back up locally and upload to OSS.

3.3 Import the backup in the ApsaraDB RDS console

1. Log in to the ApsaraDB RDS console. In the top navigation bar, select the region of your destination RDS instance. In the left-side navigation pane, click Backups.

2. On the User Backups tab, click Import Backup.

3. In the Import Guide wizard, read the instructions and click Next until you reach 3. Import Data.

   Steps 1. Back Up Source Database and 2. Upload Backup Files to OSS in the wizard correspond to Steps 3.1 and 3.2 in this guide.

4. In the 3. Import Data step, configure the following parameters and click OK.

   If ApsaraDB RDS is not authorized to access OSS, click Authorize at the bottom of this step. On the page that appears, click Confirm Authorization Policy.

   Parameter	Description
   MySQL version	Displays 5.7/8.0 automatically. Both MySQL 5.7 and MySQL 8.0 are supported.
   Region	The region of the OSS bucket that stores the backup file. Must match the region of the destination RDS instance.
   OSS Bucket	The OSS bucket that contains the backup file. See Upload objects for details.
   OSS file name	The backup object in the OSS bucket. Supports fuzzy and exact match. The file must be in _QP.XB format, or compressed as TAR.GZ.
   Note	An optional description to help identify the backup file.
   Zone	The zone of the OSS bucket. Selecting a zone lets ApsaraDB RDS create a snapshot in seconds, reducing import time. The new RDS instance is created in this zone.
   Storage Capacity	Storage required for the backup file. Valid values: 20–6000 GB. Defaults to 3× the backup file size (minimum 20 GB).

5. On the User Backups tab, wait for the Status of the verification task to change from Verifying to Completed.

   Important

   Verification time varies. Instances with high write activity or large transactions during backup may take longer to verify.

6. Find the backup file and click Restore in the Actions column.

7. Configure the following parameters and click Next: Instance Configuration.

   Parameter	Description
   Zone of Primary Node	The zone for the primary RDS instance. Displayed only if you did not select a zone when importing the backup file.
   Storage Type	ESSD PL1: A performance level 1 Enterprise SSD. Standard SSD: A standard elastic block storage device. See Storage types for details.
   Instance Type	General-purpose (Entry-level): Exclusively allocated memory and I/O, with shared CPU and storage. See Primary ApsaraDB RDS instance types for the full list.
   Storage Capacity	Storage provisioned for data files, system files, log files, and transaction files. Adjustable in 5 GB increments.

8. Configure the following parameters and click Next: Confirm Order.

   Parameter	Description
   Network Type	Select VPC. A virtual private cloud (VPC) provides higher security and better performance. You must also configure VPC and vSwitch of Primary Node. The RDS instance and any ECS instance you want to connect must be in the same VPC.
   Parameter Template	A system or custom parameter template. See Use a parameter template.
   Time Zone	Time zone for the RDS instance.
   Table Name Case Sensitivity	If table names in the source instance are case-sensitive, select Case-sensitive to maintain consistency.

9. Confirm the instance configuration in the Parameters section, set Purchase Plan, accept the Terms of Service, and click Pay Now.

   ApsaraDB RDS takes 1–5 minutes to create the instance.