Floating IPs for managed database?

I have setup a postgresql database cluster to do some testing. I tried to restore from a backup. This created a second cluster. Can somebody explain which database cluster is now the primary one? The original cluster or the one recovered from the backup? Also, how does DO guaranty that the fqdm is always the same? It looks like floating ips can’t be used with databases. In any case the fqdm should always be the same no matter what happens (failover, restore from backup, … ) to the database. Thanks Roland

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer


The DigitalOcean Managed Databases automatically handle recovery from hardware and software failures by replacing degraded nodes with new ones that resume directly from the point of failure. This does not include an FQDN change.

However, to recover from situations like a database administrator or application accidentally destroying data, you can manually restore the database cluster from backups to a new cluster. In this case, a new cluster with your backup data, but with a new FQDN is created.

Once you restore to a new cluster, the new and the old clusters are not connected. So both clusters are active.

You can not use a floating IP with the Managed Databases, but you could suggest this as an idea here:

The best thing to do to get your voice heard regarding this would be to head over to our Product Ideas board and post a new idea, including as much information as possible for what you’d like to see implemented.

Hope that helps! - Bobby.