High availability is about more than making sure that apps can get to your data even if there is a failure.
- How about when you are upgrading your database schema?
- What if you need to add memory to a database server or reconfigure/restart MySQL?
- If your apps want to read data from a MySQL slave, how can you be sure they are not reading stale data without re-coding your apps?
- What if your main data center takes a hit?
- And what if you want better MySQL stability, performance, and simplified administration, but you cannot or do not want to re-write your apps or convert your current data to run with a proprietary MySQL re-write or a promised new version of MySQL?
During this webinar, we go through a detailed case study to show you how you can start with the MySQL version/variant (MySQL Community 5.x, MySQL Enterprise 5.x, MariaDB, Percona Server), along with the data and apps that you already have, and iteratively build up a highly-available, scalable, multi-site database infrastructure where you can perform complex data management tasks with single commands.
See live demos of the following:
- Transition from MySQL 'native' replication to a Continuent Tungsten cluster with zero app downtime
- Reading consistent data from slaves without app changes (SmartScale)
- Schema upgrade on the master database server with no app downtime (switch operation)
- Automated fail over when a MySQL database server crashes
- Recovery of a failed master to a fully operational slave with a single command
- Switch of database operations to a remote site with no app down time (geo-clustering, cross-site 'switch' operation).