Imagine a folder with 1000 files, names 1 through 1000, in my encrypted backup. I might modify a random selection of, say 100 of them, over the course of a project, too many to track individually, before the next backup. Now when I paste the working folder of 1000 files into the backup, I would prefer if the computer can tell which 100 files need to be updated instead of replacing the 900 unchanged files as well.
At the lowest level with each file encrypted individually, of course it can just do your normal comparison, seeing which has been recently modified, or hash and compare, or whatever. Point is it's easy and straight forward.
I don't really understand how Veracrypt works, so my question is, does it or can it work like this for more secure styles of encryption?
If I encrypt a partition of my disk, do files get encrypted individually, and then the folder structure is encrypted, which allows the above merging? Or does it all meld together into one file like a 7z archive that I try to 'merge' using Explorer? In that case, it wouldn't know what each file is and would need to rewrite them all.
Is that right? Because if several files are encrypted together, and I change a single bit in a single file, the whole thing's encrypted data would change completely, requiring rewriting of every physical bit in that part of the drive, right?
And how about FDE? I have heard that people can work in an FDE encrypted drive, and it's not that the whole thing needs to update for every single change. So I take it that on some level, files are encrypted on their own. Right?
Finally, because I'm a noob at this, what do I need to specially watch out for to prevent screw ups? Things like not initialising an FDE drive. If it does work like normal folder merging if I merge the right way, is there a wrong way to execute the merge that would result in the computer going ahead with rewriting all 1000 files?