Aster Database:
Always On for 24x7 Big Data Analytics

The Availability Challenge

Your customers demand access to your business 24x7. Why should your analytics be any different? It’s critical for your systems to support your users and the analytic applications that they rely on for answers.

The Always-On Approach

Aster Database was designed from the ground up to avoid unplanned outages due to hardware and software failures, user or administrator error, and local or site disasters. In addition, unique capabilities for live administration minimize or altogether avoid even planned outages. As the system scales - to 100 servers, 1000, or more - administration overhead remains constant. Here’s how:

  • Recovery-Oriented Computing (ROC) – Aster Data leads the industry in massive-scale fault tolerance with replication, automatic failover, NIC bonding, failure heuristics, and clustered backup preventing unplanned downtime due to hardware or software failures.
  • Consistent Performance – Intelligent load redistribution upon failure minimizes overhead on surviving nodes, with parallel replica restoration allowing immediate recovery to optimal system state.
  • The End of Maintenance Windows – Simultaneous load/export during queries, online backup and recovery, online restoration, and online scale-out eliminate the need for scheduled downtime.
  • One-Click Management – Aster Management Console offers an intuitive web interface for ultra-simple operations: add node (scale-out), remove node (swap-out), restore replication (resilience), backup (data protection), and restart (upgrade).

Aster Database minimizes both planned and unplanned downtime

Want to Learn More?
    1.888.Aster.Data
    info@asterdata.com Demo
The Best Insights Possible
Data Sheet:
Aster Database
Analytic Platform
Technology Brief: Aster Database – "Always On" Availability
Technology Brief: Aster Database – Manageability
Technology Brief: Aster Database – Online Backup
We've been very pleased with both the reliability and availability of Aster nCluster. We've had cases where disks and other components have failed in our cluster, but the database has kept on going answering queries with the same performance as before.

aggregate knowledge
Kris Wehner, CTO