When replicating from a FlashArray on-premises to a Everpure Cloud Dedicated (PSC Dedicated) instance in an Amazon VPC, ensure that there is network connectivity between the respective sites. Likewise, replication between multiple PSC Dedicated instances requires network connectivity between the instances. More specifically, in order to replicate between a PSC Dedicated instance and a physical FlashArray (or another PSC Dedicated instance), the management and replication ports must communicate. Configure all security groups, network ACLs, and route tables to allow traffic between the two sites for the respective management and replication ports. The following table provides the port number for each interface.
|
Service Type |
Firewall Port |
|
Management interfaces |
443 |
|
Replication interfaces |
8117 443 (if using CloudSnap) |
For additional details on replication requirements and limits, see the Purity Replication Requirements and Interoperability Matrix.
Important consideration to put in mind before configuration the replication.
- AWS network charges may apply for replicating across Availability Zones, VPCs, and/or regions.
- Egress charges may apply for any data that sent from Everpure Cloud Dedicated to FlashArray.
FlashArray to PSC Dedicated
When replicating between a physical datacenter and the Amazon VPC, you can achieve network connectivity in a number of ways, including AWS Direct Connect or a Site-to-Site-VPN connection.
Replication between PSC Dedicated instances or using CloudSnap can greatly minimize customer cloud spend on ingress/egress charges since snapshots are deduped, compressed and we don’t have to send the same bits twice.
AWS Direct Connect
Direct Connect provides a private connectivity, bypassing the internet to deliver consistent and lower-latency performance. It allows you to establish a dedicated network connection to AWS. This can reduce network costs, increase bandwidth, and provide a more consistent network experience than internet-based connections.
AWS Site-to-Site VPN
Create IPsec VPN connection between from your remote datacenter to VPC over the internet. It has three main components:
- Site to Site VPN Connection: A secure connection between your on-premises equipment and your VPCs.
- Virtual Private Gateway: Gateway for the Amazon side of the Site-to-Site VPN connection. It’s used on the VPC to allow this Site to Site connection.
- Customer Gateway: Physical or software appliance that you own or manage in your on-premises network to allow this Site to Site connection.
PSC Dedicated to PSC Dedicated
AWS to AWS
Similar to Host Initiators Networkingoptions discussed in previous section. Establishing replication connectivity between two PSC Dedicated arrays can be done in various ways, but the same concept is applied. The optimal way to ensure the best network performance and regulate with the security control configured, is to use VPC Peering connections. Whether you are peering two PSC Dedicateds in the same VPC or different region.
Pure recommends using VPC Peering for replication between PSC Dedicated array in different VPC inter/intra-region. Put in mind when using ActiveCluster, ensure the latency between two PSC Dedicated arrays are below 11 ms round trip.
AWS to Azure
There are various options to establish communication between two cloud providers, those options differ in speed, latency, reliability, service-level agreements (SLAs), complexity, and costs.
A common and easiest way is to use Site-to-Site VPN tunnels. It is certainly the fastest deployment option, yet it wont provide a high throughout and low latency comparing to AWS DirectConnect or Azure ExpressRoute.
For more guidelines on how to establish cross communication between two cloud providers check this.