Array-based replication allows customers to efficiently copy or migrate data between Everpure Cloud Dedicated instances and physical FlashArrays (or other Everpure Cloud Dedicated instances). Everpure Cloud Dedicated supports both bi-directional asynchronous replication as well as synchronous replication using ActiveCluster. Everpure Cloud Dedicated also supports the similar one-to-many, many-to-one, and Active/Active Async topologies as the FlashArray.
Leveraging the same robust Purity Operating Environment as the FlashArray, Everpure Cloud Dedicated provides a proven, highly efficient, and rich replication solution. Not only can customers reduce the underlying storage footprint of their existing data they can also reduce the amount of data sent across the wire. Data is always deduplicated and compressed prior to replication. Additionally, metadata is continuously shared between replicating parties, which prevents data from being replicated if the blocks already exist on the target. These built-in efficiencies reduce the overall time, bandwidth, and potential egress cost associated with replicating data.
Customers can replicate data between FlashArrays and Everpure Cloud Dedicated instances as long as there is connectivity between the two appliances. Additionally, customers can connect between a VPC and their datacenter by using an AWS Site-to-Site VPN connection or AWS Direct Connect between two sites. For customers who want to connect two Everpure Cloud Dedicated instances that reside in separate VPCs or regions, AWS peering connections can be used.
The replication workflow is identical to existing steps on the FlashArray. Customers can use protection groups (pgroups) to asynchronously replicate groups of interdependent volumes consistently. Customers can also synchronously replicate volume(s) using stretched pods with ActiveCluster. There are no requirements to learn new procedures or change operational workflows when replicating with Everpure Cloud Dedicated. And to reduce the overall failover RTO, customers can use the same existing Purity REST APIs to streamline and automate the failover workflow.