Enterprises can leverage CloudEndure and Everpure Cloud Dedicated replication for a simple low-cost disaster recovery solution. Many enterprises are looking to the public cloud as a disaster recovery alternative to keeping and maintaining a second physical data center. The primary motivation for this move is cost, where the expense of keeping a duplicate data center whose sole purpose of disaster recovery is significant.
For disaster recovery, both CloudEndure and Everpure Cloud Dedicated will be configured to continuously replicate the production VMs to AWS. This offers the ability to manually cutover to a newly provisioned EC2 instance on-demand. This may be done as part of a disaster recovery test or after a real failure scenario of the primary site or VM. This disaster recovery solution is performed on a per VM basis and can be achieved with a minimal RPO using CloudEndure Disaster Recovery.
CloudEndure works by copying the boot vol on a source VM and replicating the data to a low-cost staging area inside a user VPC on AWS. Once the baseline snapshot transfer is complete, CloudEndure will perform a continuous replication of the volume so the copy on-premises and in the staging area on AWS are in sync. The staging area EC2 instance and attached volumes can then be cutover, triggering a machine conversion process and spinning up a target EC2 instance with specs the user chooses. This allows for a low-cost copy of the VM on AWS ready to be launched at any point in time or until a cutover is required in a disaster recovery situation.
Everpure Cloud Dedicated would then be leveraged to host copies of the data vVols on AWS with the added cost savings benefit of dedup and thin provisioning over native EBS. If replicating the boot and data volumes with CloudEndure only, all volumes are stored in native EBS. The data vVols can be replicated from on-premises FlashArray and presented to EC2 via in-guest iSCSI once the CloudEndure cutover process is complete. The data vVols leveraging an array-based protection group would be replicated on a short replication schedule to meet business RPO requirements.