In certain scenarios after a storage vMotion, discrepancies may be observed in the perDatastoreUsage values reported by vCenter and Aria Operations.
While vCenter displays the correct values in the UI, the Managed Object Browser (MOB) reflects the incorrect values — which is consistent with what Aria Operations reports.
This can be verified by checking the MOB path: https://<vCenter-FQDN>/mob/?moid=vm-#####&doPath=storage.perDatastoreUsage.
vCenter 8.x
Since the value is incorrect in the vCenter MOB, Aria Operations also reflects it inaccurately.
This behavior may occur if vpxa fails to refresh storage properties after a storage vMotion in certain scenarios. However, the exact root cause is still under investigation
Resolution:
Please reach out to Broadcom Technical Support to investigate this issue further.
Workaround:
Restarting the management agents on the ESXi host should display the correct values