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.

@kienht Ah, sorry RAW block devices are not supported in the SSH Transfer method. Documentation mentioning only disk image files we will change this for better understanding.

@KLM You can delete backups by removing VMs from the list in the Instances tab.

@KLM Also if you selected the "backup destination for cloud" lever in the backup destination configuration it would be only visible for cloud instances.

@benitowarez We are investigating but it looks like some error on the VMware side, did this error occur for particular VMs or all VMs ?

Hi, For the libvirt strategy only, QCOW2/RAW files or Ceph RBD are supported as the backend.

Yes, it is possible, did you choose node configuration for this backup destination? Can you give me your version of SBR?

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.

https://storware.g*tbook.io/backup-and-recovery/protecting-virtual-machines/virtual-machines/red-hat-virtualization#disk-attachment-with-proxy-vm

@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.

@benitowarez oh so after the update you still get this DISK_HANDLER error?