Why Datos IO?

Enterprises are adopting high-volume, high-ingestion and real-time applications on distributed databases. As migration to this data-centric IT infrastructure increases, enterprises must ensure that data can be managed at scale without data loss and application downtime.



your data at any granularity
and at any point in time



downtime by recovering
in minutes, not hours



DevOps and IT efficiency for
continuous delivery

1. Install and Deploy

Scale-out software-only deployment that reduces deployment time and provides high-availability

  • Multiple databases supported: Apache Cassandra (DataStax Enterprise) and MongoDB
  • Lightweight application listeners that communicate with data source via well-defined interfaces
  • Multiple options for secondary storage with both NFS and S3. Provides flexible deployment for either on-premise or public cloud.

2. Configure

Easy to configure and flexible to use

  • Add your database clusters to RecoverX environment in minutes for operational recovery needs
  • Flexibility to configure different secondary storage targets¬†depending on retention periods
  • Software-only platform enables multiple deployment scenarios including: On-premise, Iaas and PaaS environments (AWS, GCP, others)

3. Version

Backup at any interval and at any granularity

  • A point-in-time cluster consistent backup that reduces application downtime.
  • Backups are always available in native formats that results in no vendor lock-in.
  • All backup operations are resilient to failures scenarios of node and database failures.
  • Backups are highly space efficient with industry-first semantic deduplication

4. Recover

Scalable and Reliable recovery in minutes, not hours

  • Recover back to production database with same or different topology
  • Recover back to the non-production or test/dev database with a same or different typology configuration
  • Recovers data directly from secondary storage to the database resulting in reduced RTO.
  • All recovery operations are resilient to failure scenarios of node and database failures

File Origin: page.php -- Child (Default Template)