Size on disk value related to cloud libraries is incorrect

@Onno van den Berg , can you share the case number?  I’d like to take a look and track it.

Thanks!

Dammmm you're right! I just learned something today…. Why did they decide to disable it by default??? It's indeed disabled so I will turn it on and will see what happens. 

Ok, so we have another environment that was deployed very recently running FR28. The option is enabled and I see the deviation there as well. 

Cloud library with 5 buckets reporting a size on disk of 426GB. Looking on the S3 side the sum of all buckets is 583GB. I will update the ticket with these findings as well. 

I think I am right in saying that back in the early days of cloud a decision was made to limit anything that may incur a cost. As cloud platforms matured and cost  mechanisms were better understood api calls are peanuts in the scheme of things and the change was made to the default setting. It makes sense for that setting to have been enabled as part of a Service Pack upgrade but then we all complain to our dev guys when they do those sort of things as part of SP or FR upgrades. So the best option they have is to change it only for newly deployed platforms.

My 2cents

Niall 

Well in that case I would have expect the value to be reset to zero or to make it more clear being replaced by disabled. Now it is reporting an incorrect value which doesn't make sense. 

Anyway I enabled it and still see a huge and thus incorrect size being displayed. So I updated the ticket will all information! Would be great if others can also lookup their presented and actual figures. 

I have opened a ticket which has been escalated to engineering already. Will keep you posted!

Update: we turned on the setting on the 2 older CommCells and after a few days it displayed the correct figure, both running FR26 with the latest MR. Our test CCID runs FR28 and had the setting turned on already since the start but the value I'm seeing there is incorrect and way of target. I suspect the size calculation hits an issue because we have 2 cloud libraries and 1 of the 2 is attached to a MA that is turned off already for weeks. 

I also questioned the current decision to turn it off on CommCells with have been migrated from an older version and how they implemented this Instead of restten the stats to 0 or even better changing it into disabled they now show a value which is incorrect which makes it all very confusing. I also brought up the point to offer a refresh statistics button on the cloud library so you can refresh the value on-demand.

To be continued! 

Hey @Onno van den Berg , can you share the case number?  That way I don’t have to bug you for status updates 😁

Found the case and added it on the moderator side of the thread.

I’ll keep an eye on it.

FYI the root cause was found and the issue was solved by enabling:

Process volume size updates for cloud mount paths

The CommCell in where we saw an issue with the media size calculation was our test environment which was down for a long period of time following an unsuccessful upgrade towards a version that was still under development. We didn't had time to fix it immediately and decided at a certain point in time to perform a full recovery using an old DR set. Commvault uses the information from its own database to calculate the media size hence the mount path contained a lot of waste. 

I still do not understand development took this approach to disable it for older CommServe installations and still showing incorrect/inaccurate information instead of resetting the figure to 0 or displaying DISABLED.