I have two jails.
They show compression, but the pool ‘outside’ does not.
I can’t have compression active, as my backup solution complains about sparse files.
So I turned off all the compression I could find, and then deleted all the files that I want to backup.
The extest-backup folder works, they are not very big.
But the backup folder does not, and that is a huge folder.
How do I get this solved?
Yeah, no, that’s wrong. Compressed files are not sparse. And your backup solution is not worth even looking at if it can’t deal with something as simple as a sparse file.
Ok, so a bad backup solution, I know that, I can’t change it, it’s veeam.
I can’t do a direct backup from truenas to it, I have to mount the nfs exports on an ubuntu, that veeam can backup, it’s a bad setup, but I have no way of getting around veeam, and I can’t get veeam to backup directly from truenas.
So what to do?
It’s hard to say, but compression is not the source of whatever the exact problem is. Probably best to keep it enabled.
As for how to address your issue, that will depend on what is really going on with said supposedly sparse files. Are they really sparse, i.e. do they have holes in them? Is there a way to mount the NFS share without reporting holes in files?
I haven’t been able to find a mount option for the ubuntu that would circumpass that.
I wonder if I have to give up on Truenas, and just make a vmware with two ubuntu’s.
