I just checked my instance and for some reason it is backing up now. The jobs are still running, but they are not failing yet. I do not recall making any changes since the last communication and I will continue to monitor for results.
@tanawat do you have the same error during backup?
Can you send the log from Node (/opt/vprotect/logs/node_name/vprotect_daemon.log) and from vmware service (/opt/vprotect/logs/vmware/vprotect_vmware.log) ? We need log just after the backup.
@grover I see in the sent logs that you have a CDROM with the centos system image connected to this virtual machine. It's possible that this is the problem. Please disconnect the CDROM drive from the virtual machine, perform inventory synchronization in SBR to be sure and then try to make a backup.
@Cristian-Eglue Yes I can see thank you. So in this configuration, you set 7 days and 14 versions to keep, but your scheduler is configured to make a backup every day. So after a week, you have 7 backups but you also set a time restriction so backups older than 7 days will be marked as expired and removed after the next backup cleanup job so you only get 7 versions, not 14. nevertheless, you should be able to restore from any of those 7 versions.
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.
Unfortunately, at the moment it is not possible to backup only organization sites. You can use Auto-a*signment to automatically back up new sites, but all sites will be backed up. We are considering changing this in future releases.
First of all, I would ask you to confirm whether the backup method "Export storage repository" is used.
The file /etc/exports should be on the vm where the node is, I would ask you to use the command "cat /etc/exports" and "id vprotect" and send the result.
Na początku prosiłbym o potwierdzenie, czy wykorzystywana jest metoda backupu "Export storage repository".
Plik /etc/exports powinien znajdować się na vm gdzie jest node, prosiłbym o użycie polecenia "cat /etc/exports" i "id vprotect" oraz przesłanie rezultatu.
Good to hear that you like our solution. Of course, we also support the backup of single ESXi instances, without using vSphere. Unfortunately, it's hard to say now why you couldn't save these ESXi settings. If you have this problem again, please send us a screenshot of what it looks like and, preferably, the logs from the /opt/vprotect/logs directory. It's probably just a configuration issue.