Size of a stub file

The 'real' size of the file on disk is 1500 bytes if the file is in a 'purged' state (if you see a black clock icon the file is 'purged'). There used to be a feature to supress the file size fixup in explorer but the feature has since been removed from DX. Hope this helps.

Depending on the information in the file properties, the file stub size can change. Direct Read enabled/disabled, media name(s), file stream information, retention period, etc...

With regards to Direct Read, you should not be using Direct Read to manage your disk space on the Extended Drive. Direct Read is meant for use in conjunction with applications that support Byte Offset Read (such as EMC EmailXtender). You should configure Purge Rules in DiskXtender to effectively manage the used space on the Extended Drive.

Hope this helps.

-Mike

Does the size of a stub file differ if you use direct read vs. just purging the file? It seems that the total disk space on an extended drive actually increased after a move and purge using the Direct Read. Can you explain what is really being reported and what is disk space there really is when a file gets purged? Is there any reason that I should shy away from using direct read for multiple file types on a clustered file server? I currently have 85% of our data moving to a separate file server. I plan to move 15% of the other data that needs to be simply archived and never accessed again to WORM Tape.

Thank you,

Bob

Thank you for the reply. I have done both direct read and purge file. It seems that the file size does not change regardless. I assume that this is just showing the information but it appears that when I do a show properties of the extended disk the size is still the same after the purge. Also if I are the stub files different if I set the move options on a move rule to purge files immediately after a move the same if I setup purge rules separately and leave this box unchecked?

Thanks,

Bob

The size of the stub file should not change based on the setting in the move rule (at least during my testing it did not).

Also, if you write a file to media, and it is in a "fetched" state, you should right click on the Extended Drive in Windows Explorer and note the "Used Space" statistic. Then, right click on that file in Windows Explorer, choose "DiskXtender -> Purge Files" from the fly-out menu, and purge the file.

Once this is done, you should once again get properties on the Extended Drive in Windows Explorer, and see that there is less "Used Space" now that the file is purged.

Hope this helps.

-Mike