对数据库的故障转移支持 [英] Failover support for a DB

问题描述

我们当前正在评估不同数据库中的故障转移支持。

我们之前使用的是HSQLDB，但似乎它不支持群集/复制。

We are currently evaluating failover support in different databases.
We were earlier using HSQLDB but it seems that it does not have clustering/replication support.

我们的要求只是拥有两台数据库服务器，其中一台仅用于同步备份，但是如果主服务器关闭，则辅助服务器应自动开始充当主服务器。

Our requirement is simply to have two database servers, one being only for synchronous backup but if the primary server is down, then the secondary should automatically start acting as the primary server.

有人针对这种用例评估过MySQL，PostgreSQL或任何其他数据库服务器吗？

Has anyone evaluated MySQL, PostgreSQL or any other DB server for such a use case?

编辑：我们曾考虑过使用MySQL集群，但现在看来它已获得GPL许可，我们将无法使用它。谁能建议可以使用的同步复制/群集解决方案？我们目前正在使用HSQL，因此在群集模式下使用HSQL的解决方案将是我们的理想选择，但我们愿意接受更改。

We had thought of using MySQL cluster but it now seems that it is under GPL license which we won't be able to work with. Could anyone please suggest a synchronous replication/clustering solution which can be used? We are currently using HSQL, so a solution with HSQL used in clustered mode will be ideal for us but we are open for change.

推荐答案

仅出于完整性考虑， H2数据库具有某些集群支持，但与MySQL相比而且PostgreSQL的功能非常有限，实际上只是故障转移。我首先来看一下 HA-JDBC 。

Just for completeness, the H2 database has some clustering support, but compared to the MySQL and PostgreSQL features it is very limited, it's really only failover. I would first look at HA-JDBC.

这篇关于对数据库的故障转移支持的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！