I have GeoDrive setup and pushing data to my Enterprise Atmos host in a push-to-cloud (stub) arrangement.
In testing; I have everything at minimal; 1 minute-etc.
I see the file get put in the local cache; then sent to Atmos; then turned into what I think is a stub file? The file icon has a gray "X" on it but the file size is the original; not a stub cut like DiskExtender did. When I double click icon I see log that it's being restored.
This sound right?
That is how it works.
When the file is a "stub", it will show in Explorer (and other places) to look like it is really there, except the "OFFLINE" attribute is set, which causes that "X" overlay in Explorer.
How is this different from Disk-Xtender?
I think that is the issue; I'm use to seeing the file go to 32Kb, however it appears with new the GeoDrive filter the files retain their original file size in Windows Explorer. Disk prop shows the full size use; so from observation perspective it seems like the drive is using actual disk space when in fact the stub files are "really" smaller than original. I think that is what troubled me because that is not the case in DX.