Remote VPSA¶
VPSA Asynchronous Remote Mirroring provides the ability to replicate your VPSA’s data asynchronously to a different Pool within the same VPSA, to a different VPSA (either locally within the same Zadara Cloud, or remotely to a VPSA located in a remote region), or even to a different cloud provider. You can replicate a single source Volume to any number of remote (or local) Mirrors.
Asynchronous Mirroring has minimal impact on IO throughput and response time from the Server perspective since the Server IO returns immediately after being written to the local VPSA storage (without waiting for acknowledgment from the remote VPSA, like is required with Synchronous Mirroring). Later, the data is synchronized to the Remote VPSA in the background.
Remote VPSA communication is strongly authenticated and secured using cryptographic protocols designed to provide secure communication over the Internet. Mirrored data is encrypted before being shipped to the remote VPSA.
Mirrored data is also compressed before being shipped to a remote VPSA in a different region, for efficient bandwidth utilization.
You can establish a “many-to-many” remote mirroring relationship for different Volumes between different VPSAs. This means that a VPSA can mirror Volumes to many remote VPSAs, while at the same time also be the Destination VPSA for other Volumes in any other VPSA.
Note
Remote VPSA communication is done over ports 1339/1340(TCP).
Connect to a remote VPSA¶
The first step to building a DR plan (i.e. setting up a Mirrored Volume on a remote VPSA) is establishing a trusted relationship between your VPSAs.
If the VPSAs are located in different Zadara Storage Clouds you will need to first assign a Public IP to each VPSA (See Assigning Public IPs for more details) alternatively.
If the remote VPSA is located in the same Zadara cloud replication can take place using the following:
Frontend network - assuming both VPSAs are sharing the same network or on different network where proper route is in place.
Using a VPSA VNI (Virtual Network Interface - additional local network interface allocated to the VPSA)
Warning
Limitation - Replication using VNI (both source and target) over different network is allowed only if a single VNI is attached to the VPSA.
Navigate to the Remote VPSAs page and click the Discover button.
Enter the following details:
Remote VPSA IP Address:
If the remote VPSA is located in a different Zadara Storage Cloud in a remote Region:
Enter the remote VPSA Public IP address. You can find it in the VPSA details in the Management console or in the remote VPSA GUI, under .
Select the “Discover remote VPSA through Public IP” checkbox.
If the other VPSA is located within the same Zadara Storage Cloud:
Enter the remote VPSA Management IP address.
In this case, do NOT check the “Discover remote VPSA through Public IP” checkbox.
Username & Password – For authentication against the remote VPSA you are required to enter the username and password of a valid user in the remote VPSA. A cryptographic hash value (using a one-way SHA-1 hash function) of the entered password is sent to the remote VPSA.
Remote VPSA Properties¶
You can review all of the remote VPSAs with which this VPSA has established a trusted relationship. For each VPSA the following details are provided:
Properties
Local ID – The VPSA ID of the Local VPSA.
Remote ID – The VPSA ID of the remote VPSA.
Name – The name of the remote VPSA.
Provider – The name of the Cloud Provider where the remote VPSA is located.
Software Version.
IP – Public or Management IP through which the VPSAs are connected.
Rate Limit (MB/s) – Maximum tranfer rate allowed for mirroring data to the remote VPSA.
Pools
Each VPSA publishes the list of Pools that can be used to provision the remote Volume.
Note
This list does not update automatically. Click the Refresh button to update the remote Pools info from the remote VPSA.
Logs
The logs related to the selected remote VPSA