I have a productive commcell, where all mount path supports drilling of holes (Sparse). When I open a mount path property in Windows, I can see "Size on disk" is much more smaller than the "Size" of the folder. The whole partition smaller than the "Size" of the folder, but of course, larged than "Size on disk".
I installed a test environment, where all mount path also supports drilling of holes (Sparse). Scheduled or manual backups are succeed and stored on mount paths. But when I open a mount path property in Windows on test MA, then I can see the "Size" and the "Size on disk" are the same. Or "Size on disk" is a bit larger. If I check a file with "fsutil sparse queryflag", then I get the response: "This file is NOT set as sparse"
My question is, when backend file sizes start to decrease? When will be sparse set on backup files, what stored on a sparse supported mounth path?
Solved
When start using drilling holes?
Best answer by Ledoesp
I think short answer is time and retention. In your test environment you run a few jobs and of course they are not aged until they meet the retention, that is why you do not see the same behaviour as in the production environment. Once some jobs are aged in the test environment, then you will start getting the sparse files. And I am assuming also you are using CommVault deduplication for your test environment.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.