Bytes written to storage grows even though backed up data doesn't change
Hello, So, a client of mine asked for help in creating a report that could help him track how backed up data has been growing, as well as how much of his storage is being used. He wants to do it per policy per month. I used Total Job Size for tracking storage usage since it only considers what is actually being stored, and Maximum Job Protected Size to estimate how much data he's backing up with the policy (it should pick up his last full backup and present it as "how much he's backing up"). Running a couple of tests, I noticed that even if the backed up data doesn't change at all (i.e. a client that hasn't been touched), the written data still changes in a way that seems almost random. I think the only thing that could be causing that is if by running manual backups for testing, something is written to storage even if there's nothing different from the last image (considering deduplication). Is there something wrong with my logic behind the report? Or is it something I'm missing about how NBU works? thanks in advance
