My Bytes Protected is actually larger than the Total Capacity. I think Bytes Protected refers to how much data Avamar holds if the data was not deduplicated.
oeps little typo in my question ( 3.1 is wrong, has to be 3.4)
yes I want to kown where the 3.9 - 3.4 = 500 GB has gone to ?
This is the only explination I can think of:
Avamar stores data in stripes/chuncks of 360 MB. These stripes/chunks always stay the same size, even when data is removed by the garbish collection.
So the 47,8% represents the total volume needed for all stripes/chunks together (and some stripes/chunks are not totaly filled up). The 3.4 GB presents the data saved in these stripes/chunks.
Didn't people worry about this 20 years ago when clusters on disks became larger when disks became larger ? Wasn't this called "slack" ? I guess not completely occupied striped would indeed be a reasonable explanation of where your 500GB went to.
Total Capacity and Server Utilization seem like they would be pretty easy for Avamar to calculate, so I would trust those numbers most. If you think about how Avamar works, Bytes Protected is probably a much more complicated calcuation. Obviously, it is calcuated separately, rather than simply Total Capcity * Utilization.
Also, it does not seem to be calculated consistently in different places. On my system, today's Bytes Protected Client report shows 2148 GB protected, but Avamar Administrator \ Server Management reports 1.6 TB protected.
alias23122
139 Posts
793
0
Posted April 1st, 2010 07:00
My Bytes Protected is actually larger than the Total Capacity. I think Bytes Protected refers to how much data Avamar holds if the data was not deduplicated.