vPlus supports Catalogic vStor Server and integrates with it with extended File System Backup Destination logic.
You can use Catalogic volumes like any other file system (mount a single volume over NFS) or you can use the scripts provided to automatically create and replicate volumes whenever vStor volume is being accessed. This documentation describes a setup with 2 vStor servers and a 1-volume-per-VM approach (with optional replication).
vPlus accesses vStor Servers using SSH public key authentication - first generate the key:
sudo-uvprotectssh-keygen
Add the VM fingerprint to the SSH known_hosts on the node for the primary (and optionally secondary) vStor Server:
It must be a known_hosts file that belongs to the vprotect user
sudo-uvprotectssh-oHostKeyAlgorithms=ssh-rsa[email protected]#The authenticity of host '10.10.10.1 (10.10.10.1)' can't be established.#RSA key fingerprint is SHA256:65M/6jNBXJTFqti/798STSFeZigRzHMivDNl0t95FNI.#RSA key fingerprint is MD5:cc:91:7d:17:8e:21:68:19:4b:c9:e4:76:bd:f5:4d:fc.#Are you sure you want to continue connecting (yes/no)? yes#Warning: Permanently added '10.10.10.1' (RSA) to the list of known hosts.
Copy the key to each vStor Server:
sudo-uvprotectssh-copy-id[email protected]#/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/opt/vprotect/.ssh/id_rsa.pub"#/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed#/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys#[email protected]'s password:#_#Number of key(s) added: 1#_#Now try logging into the machine, with: "ssh '[email protected]'"#and check to make sure that only the key(s) you wanted were added.
Open the Backup Destinations section on the left menu.
Create a new Catalogic vStor Server Backup Destination (choose from the top-right drop-down menu).
Fill in the template with your information.
FIRST_VS_HOST - your primary vStor Server IP/hostname
SECOND_VS_HOST - optional, secondary vStor Server IP/hostname, where the data will be replicated to
VS_PARTNER_ID - optional, secondary vStor partner ID - you can get this ID by running this command on the vStor Server shell:
If a secondary server is not provided, vPlus will assume that no replication is needed.
Initiate backup to test if the scripts have been executed correctly - in the vprotect_daemon.log files, you should be able to see messages like this:
