Bermigrasi dari Amazon Aurora MySQL tanpa hak istimewa SUPERUSER
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat Anda membuat dan menjalankan tugas migrasi dengan sumber MySQL Amazon Aurora atau
sumber yang tidak mengizinkan hak istimewa SUPERUSER, migrasi dapat memerlukan langkah tambahan.
Membuat tugas migrasi Amazon Aurora MySQL
Pastikan Anda mempertimbangkan persyaratan berikut dan menyesuaikan proses migrasi:
MySQL membatasi definisi nama host sumber hingga 60 karakter. Nama host database
Amazon Aurora biasanya lebih dari 60 karakter. Jika hal ini terjadi untuk database yang Anda migrasikan, konfigurasikan pengalihan DNS untuk membuat data CNAME yang mengaitkan nama domain Anda dengan nama domain instance database Amazon Aurora Anda. Untuk informasi selengkapnya tentang cara menyiapkan CNAME DNS, lihat dokumentasi Cloud DNS atau dokumentasi AWS Route53.
Log biner harus disimpan di penyimpanan blok standar dan tidak dapat disimpan
di Amazon S3.
Membuat tugas migrasi berkelanjutan dengan dump manual yang disediakan memerlukan
GTID diaktifkan. GTID_MODE harus berupa
ON, OFF, atau OFF_PERMISSIVE.
Nilai GTID_MODE dari ON_PERMISSIVE tidak didukung.
Untuk mengambil dump lengkap awal, hentikan penulisan MySQL Amazon Aurora di database sumber selama kurang lebih 20 detik.
Database Migration Service tidak dapat memigrasikan data dari instance replika hanya baca Amazon Aurora dari cluster database MySQL karena
file log biner tidak dapat diambil dari instance. Untuk informasi selengkapnya, lihat dokumentasi Amazon tentang
mengonfigurasi logging biner Aurora MySQL.
Menjalankan tugas migrasi
Untuk mengambil dump lengkap awal, hentikan penulisan MySQL Amazon Aurora
di database sumber selama sekitar 20 detik. Anda dapat menggunakan skrip yang
menemukan aktivitas tulis untuk memverifikasi bahwa semua penulisan ke database sumber dihentikan.
Indikasi kapan harus menghentikan dan melanjutkan penulisan ada dalam status dan substatus
tugas migrasi. Perubahan status dapat dilacak di API, Konsol, atau langsung di Cloud Monitoring:
Setelah status berubah menjadi Starting | Waiting for source writes to stop,
penulisan harus dihentikan ke database sumber. Database Migration Service mengidentifikasi bahwa penulisan dihentikan, dan statusnya berubah menjadi Running | Preparing the dump.
Setelah status berubah menjadi Running | Full dump in progress, Anda dapat melanjutkan penulisan ke database sumber dengan aman.
Database Migration Service terus mencoba mengambil dump awal selama sekitar 20 menit. Jika operasi tulis belum dihentikan, atau jika operasi tulis dilanjutkan sebelum pembaruan status, proses akan gagal dan menampilkan error yang menjelaskan penyebab kegagalan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eMigrations from Amazon Aurora MySQL sources without SUPERUSER privileges require specific adjustments to the migration process.\u003c/p\u003e\n"],["\u003cp\u003eSource hostnames longer than 60 characters require configuring a DNS redirect with a CNAME record.\u003c/p\u003e\n"],["\u003cp\u003eBinary logs must be stored on standard block storage, not Amazon S3, for migration jobs.\u003c/p\u003e\n"],["\u003cp\u003eFor initial full dumps, it is necessary to stop writes to the source MySQL Amazon Aurora database for around 20 seconds, using scripts to identify when to stop.\u003c/p\u003e\n"],["\u003cp\u003eDatabase Migration Service cannot migrate data from an Amazon Aurora read-only replica instance because it cannot retrieve binary log files from the instance.\u003c/p\u003e\n"]]],[],null,["# Migrating from Amazon Aurora MySQL without SUPERUSER privileges\n\n\u003cbr /\u003e\n\nWhen you create and run a migration job with an Amazon Aurora MySQL source or\nsources that don't allow SUPERUSER privileges, the migration can require additional steps.\n\nCreate the Amazon Aurora MySQL migration job\n--------------------------------------------\n\nMake sure you consider the following requirements and adjust your migration process:\n\n1. MySQL limits the source hostname definition to 60 characters. Amazon Aurora\n databases hostnames will typically be longer than 60 characters. If this\n is the case for the database you are migrating, configure\n a DNS redirect to create a\n [CNAME record](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html)\n that associates your domain name with the domain name of your Amazon Aurora\n database instance. For more information about setting up DNS CNAME, see the\n [Cloud DNS documentation](/dns/docs/set-up-dns-records-domain-name) or the\n [AWS Route53 documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-rds-db.html).\n\n2. Binary logs must be stored on standard block storage and cannot be stored\n on Amazon S3.\n\n3. Creating a continuous migration job with a manual dump provided requires\n `GTID` to be enabled. `GTID_MODE` must be either\n \u003cvar translate=\"no\"\u003eON\u003c/var\u003e, \u003cvar translate=\"no\"\u003eOFF\u003c/var\u003e, or \u003cvar translate=\"no\"\u003eOFF_PERMISSIVE\u003c/var\u003e.\n The `GTID_MODE` value of \u003cvar translate=\"no\"\u003eON_PERMISSIVE\u003c/var\u003e isn't supported.\n\n4. To take the initial full dump, stop MySQL Amazon Aurora writes at the\n source database for approximately 20 seconds.\n\n5. Database Migration Service can't migrate data from an Amazon Aurora read-only replica instance of a MySQL database cluster because\n binary log files can't be retrieved from the instance. For more information, see the Amazon documentation about\n [configuring Aurora MySQL binary logging](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_LogAccess.MySQL.BinaryFormat.html).\n\nRun the migration job\n---------------------\n\nTo take the initial full dump, stop MySQL Amazon Aurora writes\nat the source database for approximately 20 seconds. You can use a script that [finds write activities](/database-migration/docs/mysql/debugging-tools#write-activities) to verify that all writing to the source database is stopped.\n\nIndication of when to stop and resume writes is in the status and substatus of\nthe migration job. The status changes can be tracked in the API, Console or\ndirectly in Cloud Monitoring:\n\n1. After the status changes to **Starting \\| Waiting for source writes to stop** ,\n writing should be stopped to the source database. Database Migration Service identifies that the writing stopped, and the status changes to **Running \\| Preparing the dump**.\n\n2. After the status changes to **Running \\| Full dump in progress**, it's safe\n to resume writing to the source database.\n\nDatabase Migration Service keeps trying to take the initial dump for approximately 20 minutes. If writes haven't been stopped, or if writes are resumed before the status update, then the process fails and returns an error describing the cause of the failure."]]
