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,
@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?
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.
@andreargamgroup said in Problem to esport mailbox to pst file:
UnicodeEncodeError: 'latin-1' codec can't encode characters in position
Also, post the output of locale command.
Hello,
can you send storware version? Run
rpm -qa | grep vprotect
and post the output.
Hi,
I can't see the images you uploaded. Storware had some issues with duplicated rules. It was already fixed so I would recommend updating to the latest version 6.1.0 (6.0.0 will also be fine).
Hi,
this is a known error and the fix is already in the testing phase. I will let you know when it will be available for download.
Hi @matti
Disk Image Transfer requires RHV to be in version 4.3+. For version 4.2 you can only use the disk attachment strategy which gives you the possibility to do only full backups. This strategy also requires having a node installed inside the RHV cluster as a proxy vm.