Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Officially, RDS instances can't be directly set up to slave non-RDS databases.

My production master is MySQL running on Hetzner and I want an RDS instance to closely follow it for backup purposes, including for the ability to actually use the RDS as a temporary master in case of disaster recovery (e.g. by having scripts that create our complete production setup on AWS in case Hetzner has a major failure). The point-in-time restoration ability is very important as well.

We can live with a constant 5-10 minute lag between the production master and the RDS backup.

I'm looking for some ideas on how I could achieve more or less the same effect by using, perhaps, some additional tools and/or an intermediate process. I'm also open to a non-RDS solution that can provide similar benefits (but not at a higher price.)

share|improve this question

Use Tungsten Replicator - it will allow you replication from a non-RDS instance to Amazon RDS which is otherwise not officially supported, Alternatively you could try something like maatkit (now Percona Toolkit - using the pt-sync-tables command and run it on a cron or perhaps a service on a third-party device (I'm not familiar with Hetzner).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.