Although AWS is considered to be a highly reliable cloud, there are still a number of reasons your instances could become unavailable. These could include bad OS or software updates, malware, accidental data deletion, or even a natural disaster that affects an entire Amazon region. Your business should have a solution that can get your infrastructure back to a working state in a matter of minutes.
NAKIVO Backup & Replication allows you to create and maintain exact copies (replicas) of your original EC2 instances and fail over to the replicas for near-instant disaster recovery.
With NAKIVO Backup & Replication, you can eliminate the burden of manual data protection management. By setting up replication policies, you can automatically replicate only those EC2 instances that match certain parameters (name, size, etc.). NAKIVO Backup & Replication then monitors your infrastructure for new matching instances and automatically adds them to the relevant replication jobs.
For fast data transfer, NAKIVO Backup & Replication performs incremental replication. The software identifies blocks of data that have changed between the previous and current jobs. Only those changed blocks are transferred to the target location, saving significant amounts of time.
You can replicate your AWS EC2 instances from any AWS region to any other AWS region, or even across accounts. If your primary account credentials were compromised and all your AWS EC2 data got deleted (which takes mere seconds), you could immediately recover by powering on instance replicas in a different account.
NAKIVO Backup & Replication performs application-aware replication, which ensures that the data of applications and databases (such as Microsoft Exchange, Active Directory, SQL, or SharePoint) remains transactionally consistent.
For each replica, you can store up to 1000 recovery points, rotating them on a daily, weekly, monthly, and yearly basis in accordance with the GFS retention policy. If your AWS EC2 instance was damaged and then replicated, you can simply recover to a previous state where the instance was operational.
Because the replicas are regular EC2 instances, recovering from a disaster is as simple as failing over to the replicas – which is almost instant. Until they are needed, the instance replicas remain in a powered-off state; thus, you don’t need to pay for resources consumed by their operation in the DR region.