2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
The RDS team were able to resolve this for us:
For an Aurora MySQL version 2 cluster that uses backtrack, currently you can't use the snapshot restore method to upgrade to Aurora MySQL version 3. This limitation applies to all clusters that use backtrack, regardless of whether the backtrack setting is turned on. In this case, perform a logical dump and restore by using a tool such as the mysqldump command.
beantwortet vor 2 Jahren
0
Just encountered the same thing, would be nice if the AWS API rejected restoring from a snapshot that had backtrack enabled. Now we've got a cluster stuck in creating.
Can someone at AWS please delete the cluster qwertee-issue-3434
that's stuck on our account?
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
The cluster has vanished, don't know if someone intervened or if it was just some automated removal but at least it's gone!