When running the Vertica DB backup as per the documentation:
/opt/vertica/bin/vbr.py --task backup --config-file /data/backup/backup_snapshot.ini
The following error is generated:
Error: Unable to launch rsync daemon on backup host: BACKUP_HOST/opt/vertica/bin/rsync: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directoryTraceback (most recent call last): File "<stdin>", line 208, in launch File "/opt/vertica/oss/python3/lib/python3.11/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd)subprocess.CalledProcessError: Command '['/opt/vertica/bin/rsync', '--daemon', '--config=/tmp/vbr_rsyncd/vbr_rsyncd.conf', '--port=50000']' returned non-zero exit status 127.
DX NetOps CAPM 25.4.4 or later
The error:
Error: Unable to launch rsync daemon on backup host: BACKUP_HOST/opt/vertica/bin/rsync: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
shows that when attempting to run the Data Repository backup, the required shared libraries for the Vertica backup tools are missing on the remote backup host, BACKUP_HOST.
Vertica's old rsync didn't depend on libcrypto.so.3. This is required though for the latest versions for added security.
Vertica 24.4.0-x provides libcrypto.so.3 in its lib directory. And rsync has internal LD_LIBRARY_PATH for ../../lib. If not found it will look at the system libraries (openssl3-libs).
In this case, if you can't install openssl3-libs, then to get it working, you'll need to copy the file across manually from the Vertica Node to the backup host.
Or alternately, as per the Vertica docs:
Have either the Vertica rpm or Python 3.7 and rsync 3.0.5 or later installed.
But if that's not an option either, then copy across the file from Node 1 to backup:
scp dradmin@<DR_HOST>:/opt/vertica/lib/libcrypto.so.3 /opt/vertica/lib