Hello @carvalhoiv

Please tell me where is your backup destination located? Is this some local or remote resource? Can you show permissions for /vprotect_data and mounted resources? What is the exact version of vprotect packages? Please send the result of these commands:

rpm -qa | grep vprotect
ls -l /
ls -l /vprotect_data
df -h

Are you able to manually execute this vp_backup_postgresql_remote.sh script? Does the backup of the internal vprotect database work properly?

Hi @hdstart,
I believe you have version 6.2.0 in mind
If yes, please edit /opt/vprotect/vprotect.env file and uncomment below lines:

#LIBGUESTFS_BACKEND="direct"
#LIBGUESTFS_BACKEND_SETTINGS="force_tcg"

then restart vprotect-node service and rerun the backup.

Hello @victors,

This new limitation was introduced in the 6.2 version of Storware Backup & Recovery. In this strategy, you can make only full backups of OpenStack instances because every time a snapshot is kept on the VM, the disk type changes to QCOW2.

Incremental backups are only available for CEPH volumes in SSH/libvirt strategy,

https://storware.gitbook.io/backup-and-recovery/changelog

@carvalhoiv it could also be a network connection problem to oVirt manager or its hosts. To connect, we require two ports open on the firewall: 54322 and 54323. Please make sure that these ports are open on the oVirt manager and its hosts.

@andreargamgroup I can confirm that the same behavior occurs when you are using a password with UTF-8 characters. I will let you know when the fix for this problem will be ready.

@andreargamgroup Sorry for the late response. This error is thrown from the Python packages.

    if isinstance(username, str):
        username = username.encode('latin1')

    if isinstance(password, str):
        password = password.encode('latin1')

Do you have special characters in the password? If yes, can you try to set a password with only letters and check if this will work as a workaround?

Hello @user

If you still have this problem, please send us the full DEBUG logs of this operation (server and node logs). If you cannot attach logs to this thread, you can put them somewhere, e.g. OneDrive or similar, and send the link.

Here is the documentation on how to switch logs to debug: Logs in DEBUG

Ah because of the censorship copy this link and change * to s

Can you check if Winrm is configured properly? You can follow suggestions from this KB https://storware.atlassian.net/wiki/spaces/vprotect/pages/2095153400/KB+10085+Export+to+PST+-+how+to+diagnose+winrm+exceptions

Hi Ryder,
Unfortunately, the free version of ESXi is not supported.