3 ms·
I am imagining a scenario where the instance is shut down and restored to a point-in-time snapshot. The UI suggests this is possible based on the verbage, and t
by whalesalad 7y ago
I am imagining a scenario where the instance is shut down and restored to a point-in-time snapshot. The UI suggests this is possible based on the verbage, and this is an expectation of lots of other DB management tools.
At the moment, when you try and click 'Restore to point in time' it's just taking you through the new instance wizard with the snapshot being used as the initial dataset. Screenshot: https://i.imgur.com/vBiqgJg.png https://i.imgur.com/vBiqgJg.png -- the 'restore to point in time' is extremely misleading.
My specific uses case would be for PostgreSQL and/or MySQL, I do not use nor have I tried Aurora.
I can't get the S3 export to work either. Screenshot: https://i.imgur.com/nabbsMr.png https://i.imgur.com/nabbsMr.png
I need to grab a single row out of a snapshot from our staging database. So far I have restored the DB once and our QA team was able to reproduce a bug. They began testing prior to me pulling the data out, so now I am re-cloning an instance to fetch the unmolested data from that DB.
tl;dr - allow me restore a snapshot like every other piece of software that has a snapshotting component. caveat is that this will likely need to be an offline process, but as long as that is noted and clear, that is going to help a LOT of people out.
- otterley 7y ago> allow me restore a snapshot like every other piece of software that has a snapshotting component. caveat is that this will likely need to be an offline process, but as long as that is noted and clear, that is going to help a LOT of people out. We have this in Aurora already. If you migrate to Aurora (which is MySQL/Postgres compatible), you'll get this functionality out of the box.
- whalesalad 7y agoIs there a 'clone this database, but as an aurora database, and make it a replica that can eventually become standalone' feature? Most of my RDS usage is for my clients, so it is not always feasable to up and forklift them to a different database platform. I would imagine though that AWS is not going to invest a lot of time and energy into improving the developer ergonomics and UX of non-Aurora databases? I can't think of anyone who would choose Aurora right off the bat -- becuase it's one click closer to complete vendor lock-in and away from OSS.
- otterley 7y agoWe have migration instructions in the Aurora documentation. See, for example: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.html https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide... (MySQL) or https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Migrating.html https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide... (Postgres). Again, both are compatible with the open-source versions, so you can export your data if you need to via the standard tooling.
- nitesh_aws 7y agoSent you an email!