Why ExaGrid Hyperconverged Backup is intelligent
ExaGrid knows that deduplication is required, but how you implement it changes everything in the backup. Data deduplication reduces storage requirements and bandwidth for replication. However, if it is not implemented correctly, backups, restores and VM starts will be slowed down drastically and the backup window will get bigger with increasing amounts of data. This is due to the fact that data deduplication is very computationally intensive. You do not want to perform deduplication during the backup window, nor do you want to restore deduplicated data or boot from a pool.
Up to 32 devices can be combined and adjusted in a single scale-out system.
An ExaGrid system can be scaled to 2 PB in a single system.
ExaGrid can protect up to 16 data centers in a hub-and-spoke topology with cross-site replication
ExaGrid's unique approach enables all virtualized backup functions to be performed quickly, as ExaGrid maintains a full copy of the latest full VM backups in their complete, unduplicated form in an integrated landing zone, eliminating the need for time-consuming data rehydration for each request.
Distributed data center locations
All systems are managed regardless of their location via a single user interface with Internet Explorer, Chrome or Firefox.
Private cloud disaster recovery
ExaGrid supports up to 16 large data centers in a cross protection group with a master hub and 15 locations.
Over 50% of ExaGrid customers removed the tape both on-site and off-site using an on-site ExaGrid system for local backups and restores, and then replicated to an ExaGrid in a second location as a second data center for disaster recovery.
Hybrid cloud disaster recovery
Public cloud disaster recovery
A virtual ExaGrid that runs in AWS on an EC2 instance takes the replicated data and stores it in S3 or S3 IA.
The primary physical ExaGrid site replicates only deduplicated data for WAN efficiency to the virtual ExaGrid in AWS.