Aurreum database replication family welcomes a new member, MySQL data security protection upgraded

Aurreum database replication supports Oracle and SQL Server databases, offering a wide range of data security protection capabilities from logical backups, physical backups, and synthetic backups to continuous log real-time protection and remote disaster recovery.

To cater to more application scenarios and data restore requirements, Aurreum has officially launched a new database replication feature specifically for MySQL, providing more diverse protection capabilities. It offers a flexible, reliable, and secure data protection solution for users' business systems, establishing an impregnable data security defense.

Features

Aurreum’s MySQL database replication is based on MySQL binary logs. By configuring the primary-standby (source-replica) replication relationship, it can provide real-time protection capabilities with an RPO (Recovery Point Objective) close to zero. When the primary database fails, users can upgrade the standby database to take over normal business traffic. This failover process can be achieved within seconds. Additionally, Aurreum’s MySQL database replication supports a wide range of features including disaster recovery testing, reverse incremental synchronization, and replication monitoring.

Aurreum MySQL database replication features

  1. Replication modes: semi-synchronous replication and asynchronous replication

    • Semi-synchronous replication: The primary must wait for the standby to receive and log replicated events before committing a transaction.
    • Asynchronous replication: The primary does not need to confirm whether the standby has logged or processed the replication event. It does not guarantee that all replication events have reached the standby.

  2. Switching management methods: primary-standby switchover and standby activation

    • Primary-standby switchover: Users can manually change the primary and standby database relationship during the replication process.
    • Standby activation: When the primary database fails, users can activate the standby database. The replication relationship is automatically disengaged, and the standby database is into a read-write state.

  3. Reverse incremental synchronization

    When the primary fails, the standby database becomes a new primary database. As the original primary database is offline, data diverges between the new primary and original primary. Reverse incremental synchronization allows the original primary to resync only the divergent data when brought back online, instead of a full synchronization.

  4. Replication monitoring

    The key indicators monitored include resource status of primary and standby databases, database service status, replication status, replication lag. The console provides users with real-time visibility into the health and performance of the replication environment.

Typical solutions

  1. Database replication solution

    Aurreum database replication solution

    The solution enables replicating the source database to a target database. This establishes a replication relationship between the source and target databases. The solution supports read-write splitting, where write operations are executed on the source database, while read operations are executed on the target database. It improves the overall database processing performance. Furthermore, when the source database fails, the target database can immediately take over, ensuring the continuity of business operations.

  2. Database replication and backup solution

    Aurreum-database-replication-and-backup-solution

    With database backups, the solution enables restoring to any point-in-time state and addressing logical errors.

  3. Database replication and copy data management solution

    Aurreum database replication and copy data management solution

    Aurreum’s copy data management functionality allows the backup sets to be made accessible through mounting. In development and testing environments, this enables immediate access to database copies, without the need to restore. When the source database experiences logical errors, the copies can be utilized for failover, satisfying the business continuity requirements.

Conclusion

Aurreum’s newly added MySQL database replication further enriches the protection solutions, providing more comprehensive and diverse business security protection capabilities for MySQL running in complex user environments.