Hello @Tommaso

This error indicates insufficient privileges to execute this command. You probably need to use an account with higher privileges.

Hello @jguilford81

Please go to the Virtual Environments -> Virtualization Providers -> click your vCenter -> Certificates tab. Then select "Trust all certificates" and save. Perform inventory synchronization again and check the backup.

Hello @branes

What do your backup retention settings look like? With what parameters is NFS shared? Does the storware node have full access to this NFS resource? You are sure that nothing changed in the DataDomain settings in the meantime?

Hello @kirkscollision

Sorry for the late response time, I hope you are still interested in our solution.

I'm not sure what installation you're asking about. The error occurs while installing our software or XCP? Please provide more information and we will try to help.

Hello @sangram

If you select an interval schedule, the backup will be performed only at selected hours in accordance with the frequency.
For example:
Window start: 6:00AM
Window end: 10:00AM
Frequency: 60min
The backup will be performed at 6,7,8,9,10.

Perhaps the Time type with specific hours when the backup must be performed will be better in your case? You can set specific times when the backup should be performed.

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.