You are not logged in.
Hi!
I'm using XSIBackup-Free 1.5.1.9 and I am using cron scheduling. Every week when the backup runs I get an email informing me that all VMs were successfully backed up but one.
This is the error:
· windows10vm: 2022-03-28T06:21:48 | Error code 3920 at file xsibackup.c, line 3920 | Error description: XSIBackup-Free allows to backup VMs up to 100.00 GB
The VM in question has one thin provisioned hard disk assigned, with the size of 50 GB.
I don't understand why this VM is triggering a 100 GB size limit error since it's way less than 100 GB. Were do I look to diagnose and fix the issue?
Offline
Check the VM layout and the VM folders, you may have garbage files taking space.
Offline
There are no garbage files.
The du command shows 32.8 GB of files in the VM folder, and listing the folder including hidden files shows the same result.
I did however have a copy of the VM in another datastore folder but not registered as a VM if that could have an effect?
I removed it and created a job for just that VM to test and it's running. I'll see next week if my weekly backup works as expected.
Offline
That could very well be the case.
Offline
I removed the other copy on the other datastore and made sure there are no other data anywhere that can be in any way related to this VM and it still failed with the same error.
Any idea where to look next?
There are no snapshots, the datastore directory of the VM is well below 50 GB and so says the ESXi web GUI.
Offline
This is a very simple matter. (c)XSIBackup just accounts the amount of data and sets that limit. There's nothing hidden and nobody else has reported any similar issue. Examine your output thoroughly in search of clues and if you can still not find out where your data in excess is coming from, publish it here and wait for us to try to offer you some clues.
Offline
I've had similar issues. My freshly installed VCSA (no snapshots) is 57.14GB (according to VCSA itself), well under 100GB. But XSI won't back it up.
If I SSH to the ESXi host the physical size of the directory is confirmed by
[root@viking] du -sh VCSA
57.2G VCSA
But if I add up the logical size of the files it's 10x that
[root@viking] ls -al VCSA | awk '{sum += $5} END {printf "%.2f GB\n", sum/1024/1024/1024}'
597.36 GB
I'm aware ls stands for list, but in this context it works for logical size too.
Offline
It is indeed the nominal size of the disks that is taken into account.
Offline