• This topic has 2 replies, 3 voices, and was last updated October 28, 2019 by Aviv M.

de-duplication on NTFS

  • Ido C
    October 26, 2019 08:42:16 PM
    A user uploaded a bunch (perhaps several hundred megabytes of similar PDF files — drawings) today that may have caused a massive uptick in journal changes. My hypothesis is that the de-duplication on NTFS was creating a lot of extra writes. But I saw a 300 GB growth but there were not that many files. The normal journal size has been about 11 GiB.

    Tried to find sources of deletes or other things to no avail. Is my hypothesis plausible?
    As an aside, our Nimble storage now supports de-duplication so I could theoretically grow the NTFS volume and remove ntfs de-dupe.

    Jim R
    October 26, 2019 08:54:39 PM

    better phrased, can a few gigabytes of files with some potentially common data, create an exponential increase in journal size due to de-dupe?

    Aviv M
    October 28, 2019 01:54:40 PM

    The  journal size  is not only correlated to that amount of IOs that a VM is generating is a single day:

    Think of it as a buffer file before the IOs are written to the Mirror disks.

    There are additional VPG parameters in consideration that will effect the size – the expected journal history in days – max journal size or if it was set to unlimited.

    For more see the below KB

    Journal Overview, Sizing & Best Practice – Zerto Virtual Replication:

    https://www.zerto.com/myzerto/zr_td/journal-overview-zerto-virtual-replication-6_5-2/

     

     

You must be logged in to create new topics. Click here to login