vStor Partnerships
The vStor Partnerships feature lets you connect two vStor instances to facilitate the transfer and synchronization of snapshots. Once a partnership is established, you can configure a replication relationship or an offload relationship between a source volume on one partner and a target volume on the other. Volume replication is crucial for efficient data management, ensuring data redundancy and continuity across different storage environments, while offloading helps reduce primary storage usage while preserving access to historical data.
Partnerships are established at the vStor user level, meaning there can be several partnerships between any two vStor instances, provided that any user on vStor A is in partnership with no more than one user on vStor B. Partnerships are symmetrical, allowing volumes from vStor A to replicate or offload to vStor B and vice versa.
User-level partnerships enhance the possibilities resulting from vStor user roles. For example, each standard user can have different pool permissions and therefore be able to replicate only volumes from permitted pools.
Creating a Partnership
To create a new vStor partnership:
Select Partnerships from the sidebar.

Click the Add new button in the Partnerships section to open the Add New Partnership dialog window.
Enter the address of your remote partner vStor and the credentials of the user you want to establish the partnership with.
Restrictions. Partnerships cannot be established using credentials of a remote user with multifactor authentication enabled. In such a case, use an API key. See Using vStor API Keys with Catalogic DPX.

Click Save. Or go to Advanced Options (see below).
Advanced Options
The Advanced Options section allows you to configure an alternate IP address for the partner to communicate with the local vStor. You can also specify alternate ports for SSH communication.

Managing Partnerships using vStor CLI
Creating a Partnership
To create a new partnership using vStor CLI, use the following command, specifying the address, username, and password of the remote server:
Last updated