![]() ![]() It is not a fault or operation of the defrag program. Defragmenting usually involves alot of writes to the target drive so in doing so the databases hidden away in the System Volume Information will grow proprtionally. If so that works by keeping databases of the drives sectors previous contents everytime you write to the drive so it can produce a historical record of the drive that it can restore the previous state using system restore and individual files if previous versions is supported and earlier versions of the file exist that could be restored. It is one of the reasons Microsoft defragger by default does not attempt to defrag large files with fragments bigger that I think 64Mbytes as the read time is more significant as a seek and moving large chunks of data just grows the VSS protection databases eating freespace with practically zero benefit. ![]() Sonia M, would I be right in deducing that you have system restore protection enabled on the drive that lost free space during a defrag session?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |