I confirm that snapshots remain after a successful backup. i don't know if this can be a bug related to backup on thick disks.

@olivierlambert i try to rebuild xo, and make a backup again. thanks to all

e.g.

This snapshot is here from yesterday. I thought it was deleted when the backup was completed

But with delta backup in place i have double space allocated still after backup ending. is it normal? thanks

@olivierlambert olivier another (maybe last ) question, just to understand the difference between thin and thick: If I had a thin VM, taking a snapshot, would it still eats double space? thanks

@olivierlambert Historically we have always used FC even on vmware, but I might consider using NFS. Thanks a lot to everyone

@lawrencesystems you are right, but i'm using FC to have better performance.

@DustinB no i'm trying a backup via nfs to another storage.

@lawrencesystems Thank you for your answer. This is a big problem, because i need to use SAN storage, and so i can have thick VM only. I did not realize that the Snapshots was so big. what a pity...

Hi. First of all, congratulations @vates for the product. I am using XO compiled from source. I'm trying to figure out how vm backup works. I have read the documentation, but I cannot find the information I am looking for. About delta backup:

1. During and after the backup, the disk where the virtual machines reside becomes almost full. This is because the disks are duplicated and the copy remains even after the backup is finished. Is this behavior normal? If so, this type of backup is practically unusable.
2. If I understand correctly, backups are compressed. Since the storage where I go to save the files is already compressed, I would like to disable xenorchestra compression. is it possible?
3. What happens if I select more than one destination storage? Are the backups duplicated or are they spread across the different storage?

Thanks