• Improved async parallel applier performance (more than 4x throughput improvement compared to MySQL 5.5)
• Online upgrades
• Improved logging and statistics for diagnostics and trouble-shooting
• Customer requested enhancements and stability fixes

1. Online Database Provisioning with Simplified Replication Management
2. Single Unified View of the Complete Database Environment
3. Online Database Migration
4. Granular Database Monitoring
5. Online Backup with Restore
6. Integrated Configuration Management with Email-Based Alerts
7. Centralized Log Management

Download the detailed white paper in the link below
http://www.schoonerinfotech.com/resources/white_papers

http://www.schoonerinfotech.com/products/schoonersql/schoonersql_5_1

Want to know more? Join this webinar on December 14th 10am PST

https://www3.gotomeeting.com/register/988533686

We published a white paper called “Achieving Five 9s with SchoonerSQL”.  This paper describes the architecture of SchoonerSQL™, a full HA build of MySQL and its standard InnoDB storage engine. This paper then explains how to use the flexible synchronous and asynchronous replication modes in SchoonerSQL to get five nines availability. The paper then describes the recommended HA hardware setup for using SchoonerSQL.

You can download the white paper from:

http://www.schoonerinfotech.com/resources/white_papers

SchoonerSQL enhances and optimizes MySQL, going beyond to provide many unique benefits such as:

1. 99.999% availability with auto fail-over across LAN/MAN/WAN
2. Guaranteed no data loss and no stale data with “synchronous read masters”
3. High scalability and performance inside or across data centers
4. Simplified GUI to monitor and manage the entire server environment

These benefits are not available from any other MySQL distribution, with or without the various add-ons. Our rigorous adherence to MySQL and InnoDB means that database users can anytime switch from community MySQL to SchoonerSQL or back. There’s never any need to change schemas or data.

Porting data from community MySQL and InnoDB to SchoonerSQL, which is an easy step, has several benefits:

1. No migration problems
2. Zero data type changes
3. No running of special scripts or mysql_upgrade command to check in-compatibilities
4. Very little downtime
5. No need to hire special database expertise

Consider an example: If a company X is presently using community MySQL, these are the simple steps it needs to follow after deciding to use SchoonerSQL:

1. Backup data and transaction logs
2. Backup MySQL configuration file(s)
3. Uninstall community MySQL
4. Install SchoonerSQL
5. Restore saved data and transaction logs
6. Put the proper settings into the instance configuration (using our GUI or by editing the new /etc/my.cnf file)
7. Start the instance.

The same process applies to users who want to move back from SchoonerSQL to Community MySQL. No vendor lock-in.

To sum up, Schooner does not lock you in since we are fully standard based and 100% compatible with MySQL and InnoDB. Users can reap the benefits of SchoonerSQL features and never worry about vendor-lock in.

If you’re a DBA or a Developer, Schooner feels your pain. SchoonerSQL, our full high-availability build of MySQL and its standard InnoDB storage engine, includes a Cluster Admin GUI that radically simplifies cluster administration. The SchoonerSQL Cluster Admin GUI is a powerful centralized management tool that can monitor, manage, and backup your entire database servers inside the datacenter. Replication setup has never been so easy with just few clicks in our GUI.

Join this webinar (Tuesday, November 29, 2011 10:00 AM – 11:00 AM PST)
for a demo of the visually appealing SchoonerSQL GUI, and see how it makes life easy for DBAs. In this webinar we cover:

·        Schooner Admin GUI and benefits
·        GUI deployment architecture
·        Monitoring and optimization
·        1-click instance creation and database migration
·        Assigning write and read VIPs
·        Auto failover and failback
·        Integrated hot backup and scheduling
·        Full database Restore
·        Email-based Alerts

https://www3.gotomeeting.com/register/740345302

• Automatic WAN failover
• Asynchronous parallel appliers across the data center for increased throughput

Join this webinar tomorrow (November 8th – 10 am PST) to learn how SchoonerSQL 5.1:

• Maximizes service availability at high scale through its parallel threads approach
• Provides superior disaster recovery with automatic WAN failover
• Ensures no lost data
• Radically simplifies the management of MySQL clusters

https://www3.gotomeeting.com/register/635284982

• High Availability
• Ease of use
• Performance benefits

The top 10 are:

1.     Synchronous replication for InnoDB: data consistency without any data loss or any lag

2.     Auto failover inside a synchronous cluster: instantaneous and hassle free

3.     Web-based cluster admin GUI: easy and robust, with extensive displays of resource utilization

4.     Asynchronous parallel appliers for WAN replication: amazing throughput with little slave lag over WAN

5.     Immediate automatic WAN failover: seamless and automated, thereby minimizing the downtime

6.     Fast sync incremental recovery: a failed node recovers super fast

7.     One-click instance creation and VIP provisioning

8.     One-click online database migration

9.     Integrated full and incremental hot backup

10.   Email-based alerts

You can download the detailed white paper here:
http://www.schoonerinfotech.com/resources/white_papers

The term “slave” has been used in MySQL because the Slave servers have to perform every task in copying from the Master binlog, then updating their relay logs and finally committing to the Slave databases. The Master plays no role in replication here other than storing the replication events in the binlog.

This kind of Master – Slave set up imposes several limitations:
- Slave lag
- Stale or old data
- Data loss
- Manual failover which is error-prone and time consuming

In SchoonerSQL™, there is no concept of “slaves” inside a synchronous cluster. It’s far more accurate to use the term “Read Masters” because of our unique synchronous approach and replication architecture. SchoonerSQL uses a push mechanism of replication events coupled with faster processing through multiple parallel threads. This ensures that the Master and each Read Master’s data in a synchronous cluster is always consistent. So you can write data to a Master and at the same time query it from any Read Masters and get fully consistent data.

SchoonerSQL Synchronous Replication Architecture

Schooner’s approach provides several benefits:

• Zero data loss
• Guaranteed data consistency across all nodes
• No stale data
• Zero lag
• Faster response time than traditional MySQL
• Immediate automated failover to any of the nodes in the cluster, since the data is always consistent, for full service continuity.

This type of replication is very useful for Websites or Enterprises looking for a scalable MySQL – InnoDB with no lost or stale data and no slave lag.