51–60 of 67 posts
Earlier quoted context omitted.
I wonder if you could realistically do a two stage migration, X -> Amazon -> Y
Amazon probably wouldn't care if you did. They still get paid to shuffle the bits.
Earlier quoted context omitted.
You can snapshot your RDS database and restore it as an Aurora DB. Only caveat is it has to be MySQL 5.6. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora...
Not quite the same, unless I'm misunderstanding. I'm talking about an online migration on a single RDS instance with an engine switch handled fully behind the scenes. The link provided doesn't seem to handle data changes since the snapshot, and also requires a switch in the application to point to the new instance which has been restored via snapshot. DMS gets closer than the above link, I think, since it will handle…
One of the biggest problems I've had with RDS (postgres specifically) is not being able to do incremental offsite backups. I wonder if the database migration service can help with that, as they say the process is "reliable" and "automatically restarts the process and continues the migration from where it was halted"
Does anyone know how the MySQL migration & replication works under the hood? How is Amazon doing all this remotely via just a DB connector?
As for migration, don't know, you could export the database and listen to binlog but that will lock table for a bit, depending on the database size. But maybe that's acceptable.
Would be curious to hear from folks with more DBA experience :)
Earlier quoted context omitted.
Amazon probably wouldn't care if you did. They still get paid to shuffle the bits.
What they really want is keep you on RDS, not just get paid for the migration bandwidth.
In the process you need to set up an AWS account, create a RDS database, import your data into it... and perhaps you stop there despite the initial plans. Or use RDS for your next project, since you are already more familiar with it.
Earlier quoted context omitted.
Is it possible to run a read replica outside of RDS these days?
I don't see why not. Replication is just a command stream over a network. You can secure it over the daabsse's built in TLS support or over VPN. The only question is bandwidth and latency between your DC and AWS's.
Earlier quoted context omitted.
Is it possible to run a read replica outside of RDS these days?
Funny this showed up on here. I just spent the last 4-5 days playing with DMS. My company has been using AWS for a while, but management wanted a "backup" backup off Amazon "JUST IN CASE". Due to amazon blocking replication credentials for MYSQL servers we had to basically dump over scp to our off amazon server and run the update on that machine via a script. We tried a number of different options but none were relia…
We use Postgres so it might be that we couldn't do the same. Presently I run the DB on EC2 instance(s) but one day I'm sure I'll switch to RDS. Just trying to understand what an exit strategy might look like in the future.
Why is Amazon Redshift not a target for this service?
I've deployed a Redshift-based analytics application, and we're discovering operationally that -- for some workloads -- we would be better served by a Postgres RDS instance instead. It would be nice if I could one-click (or few-click) migrate everything from our Redshift instance to RDS.
Looks like this could be a better way to migrate between major versions of PostgreSQL on RDS than rolling your own.
If you didn't catch it, AWS now supports upgrades between so-called "major versions" (eg. 9.3 -> 9.4). https://aws.amazon.com/about-aws/whats-new/2015/11/rds-postg...
One of the biggest problems I've had with RDS (postgres specifically) is not being able to do incremental offsite backups. I wonder if the database migration service can help with that, as they say the process is "reliable" and "automatically restarts the process and continues the migration from where it was halted"
https://aws.amazon.com/blogs/aws/rds-postgres-read-replicas/