Actual file size vs. stub file size

I think there is some provision to create reports in DX to check on this.

I would also like to know the answer to this, because we are experiencing an issue related to your question. We are migrating to a new server, and the extended drive is a 120GB drive. We took 4 5.2GB disks and ran file restores, which should only be restoring stubs. When the restore finished, I spot checked by doing DX file properties on a few files, all of which showed purged. Yet Windows explorer now shows 20GB of disk space being used. My question is what will happen when Windows perceives this disk as being full?

the actual size of stub/tag is 4 Kb. But shows the same size as that of actual size so that it does not confuse the users.
This is because we use the Mircosoft offline attributes for offline files.

If you would like to check the size of each purge files (offline file), you can run NTFSinfo on the Extended Drive. (technet.microsoft.com/en-us/sysinternals/bb897424.aspx)

DX Shell properties and Windows Explorer properties will show the ACTUAL size of the files. The way we identify the file is a file tags is using Microsoft Offline Attribute and the little black clock located at the bottom left of the icon.


HTH

Hi everybody,

I once had a problem, where there were server snapshots saved to the extended drive (these are saved in the system volume information). So the extended drive filled up over time, though we only focused on DX and how all the space could be taken up.

I thought I share this.
Jochen.

If you want to go with the ballpark figure for the entire extended drive (not really suitable for reporting/analysis), do the properties on the disk level - used space and free space will accurately tell you what is the situation on disk after Purge has taken place.

with best regards,
Mladen