跳至内容

Cannot upgrade from mysql 8.0.34 to aurora-mysql 8.0.mysql_aurora.3.04.1. Specify a current active database version, the latest active minor version for mysql 8.0 is 8.0.35.

0

Hi all, I am trying to create an Aurora MySQL 8 instance for a RDS MySQL database and I am getting this rather confusing error message. I choose snapshot, select Action->Migrate snapshop and then I cannot fill anything into the DB engine version on the Migrate database page, but i can select Serverless v2. The RDS myql is on version 8.0.34 and Aurora does not seem to support more than migrating from 8.0.32 if you look at release notes for Aurora 3.05.1 https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.3051.html The error message seems to indicate migration is supported for 8.0.35, so i tried upgrading the db to that, but then i just get the same error again. Cant figure out how to ever migrate to Aurora, but i guess i could turn off minor upgrades on the current database and then wait for the next Aurora version to maybe support 8.0.35. Any better ideas? /Soren

已提问 2 年前4706 查看次数
3 回答
0
已接受的回答

So end the end I paused minor updates and then finally after some months Aurora MySQL caught up and now supported the version that i was on with regular RDS MySQL and i could easily migrate using a snapshop. I think this is the best way for someone that can wait a few months.

已回答 2 年前
专家
已审核 1 年前
0

To add to Regina's:

Aurora MySQL version 3.05 does not support migrating from some older MySQL 8.0 versions like 8.0.11, 8.0.13, and 8.0.15. The documentation recommends upgrading to MySQL 8.0.28 before migrating.

Even though the error message mentions 8.0.35, it's possible the underlying issue is still related to migrating from an older incompatible version. I would double check the actual MySQL version on the source instance.

Minor version upgrades can sometimes cause compatibility issues, even within the same major release. It may be better to avoid upgrading just the minor version and instead upgrade to a newer major release like 8.0.28 as recommended.

If upgrading isn't an option, another approach would be to take a snapshot of the source database, restore it to a new Aurora MySQL cluster, and then use that as the target of the migration rather than trying to migrate directly.

Checking the AWS documentation thoroughly for specific version compatibility between your source MySQL version and the target Aurora MySQL version being migrated to can help identify potential issues.

专家
已回答 2 年前
  • Hi Giovanni,

    How to "take a snapshot of the source database, restore it to a new Aurora MySQL cluster"? When I tried to restore a snapshot, there's no option to restore it as Aurora MySQL cluster. Thank you.

  • The problem the OP has is the other way around - their existing MySQL version 8.0.34 is newer than that supported by Aurora. Their Aurora version 3.0.4 is only "Compatible with Community MySQL 8.0.28".

    The fact that Aurora MySQL versions lag behind RDS MySQL versions is very annoying - I have this situation currently where I allowed my RDS db to update to latest version, but now I can't restore snapshots from that into the Aurora cluster in production :(

0

If you need to migrate asap, I could say there is another approach. It is to use a database migration tool like AWS Database Migration Service to migrate the schema and data independently of the instance itself. This bypasses the version compatibility check. You could take a snapshot of the RDS instance, restore it locally with the same version, and use a tool to migrate the data/schema to a new Aurora cluster.

AWS
已回答 2 年前
专家
已审核 2 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。