High Availability (HA) Database

Keep your businness up and running. Increase the service availability and data safety. Automatic failover with zero downtime.

High Availability Database Description

High Availability in a database refers to maintaining levels of uptime that exceed normal service level agreements. High availability databases achieve such uptime by eliminating single points of failure, reliably failing over to a redundant node, and monitoring for failures to initiate failover when needed. In practice, a high availability database is designed to run with no interruptions in service, even in the event of network latency and hardware outages.

High Availability Database Solution

HA database implementation for popluar database management systems.

SQL Server Mirroring

SQL Server Mirroring is a solution to improve the availability of SQL Server databases. It has three roles of Principal, Mirror, and Witness. The Principal can add, delete, change and check the database and provide read and write services to the outside world. The Mirror can only synchronize the database data from the Principal, and does not provide read and write services to the outside world. The Witness is used to automatically switch the role between Principal and Mirror nodes when Principal or Mirror fails.

SQL Server Always On

The Always On availability groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012 (11.x), Always On availability groups maximizes the availability of a set of user databases for an enterprise. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together.

MySQL Master-Slave Replication

MySQL Master-Slave Replication is a one-way replication (from master to slave). Only the master database is used for the write operations, while read operations may be spread on multiple slave databases. This means that if master-slave replication is used as the scale-out solution, you need to have at least two data sources defined, one for write operations and the second for read operations.

PostgreSQL Master-Slave Replication

PostgreSQL Master-Slave Replication, the slave servers are used only for read queries and when there is a fail-over. In the event of a fail-over, one of the slaves can become a master. PostgreSQL Master-Slave Replication allows changes happening in the cluster of the primary database to be copied to the standby database on another server.

High Availablity Database FAQs

Frequently asked questions about our HA database services.

More FAQs about high availability database services

Releated articles

Useful Resources about our SQL Server mirroring service.

Database Mirroring in SQL Server 2008 R2

Database mirroring is a primarily software solution for increasing database availability. Mirroring is implemented on a per-database ...

Database Mirroring Best Practices and Performance Considerations

Maximizing the availability of databases is on the top priority list for many database administrators worldwide. Database...

How to setup Database Mirroring in SQL Server 2005 using T-SQL

Our disaster recovery and database availability solution involves clustering and Database Mirroring in SQL Server 2005. At our primary ...

What is an Always On availability group?

This article introduces the Always On availability groups concepts that are central for configuring and managing one or more availability groups in SQL Server. For...

Always On availability groups: a high-availability and disaster-recovery solution

The Always On availability groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL...