+11Hello,
I've noticed that in several situations, when somethings is done through the Commcell console, there is lag until that reflects in the Command Center pane.
Why?
Is there a way to speed up this and have the information in Command center refreshed?
Example: delete a few jobs from SP. Command center disk lib usage does not reflect the change in disk usage. Commcell does.
Regards,
Pedro
Best answer by Javier
Most caches present in the MongoDB are refreshed in a 4 hrs interval.
The Command Center is indeed under constant development and we can expect all these quirks and features to get polished and enhanced with every new version that is released. It will get to a point where it will become a 1:1 substitute of the Commcell Console.
You can stop the tomcat service from webserver and perform IISRESET from CMD admin mode. Start the tomcat service again and check the status. For reports if it is getting populated with the help of private metrics reporting then try to upload the private metrics manually and check the status again in the dashboard.
Command Center relies a lot in the MongoDB, restarting Mongo should refresh the cache and should show the most recent information in Command Center.
+11Command Center relies a lot in the MongoDB, restarting Mongo should refresh the cache and should show the most recent information in Command Center.
Do you know the refresh interval? Because I noticed that from one day to another, the data was refreshed on Command Center.
+11You can stop the tomcat service from webserver and perform IISRESET from CMD admin mode. Start the tomcat service again and check the status. For reports if it is getting populated with the help of private metrics reporting then try to upload the private metrics manually and check the status again in the dashboard.
Do you know the refresh interval? Because I noticed that from one day to another, the data was refreshed on Command Center.
This is the data:
+19Unfortunately a lot of information is also populated through scheduled refresh operations who run in the backend, so you indeed see information that is lacking behind with the reality. I hope they are going solve this overtime but moving more and more towards event-based refreshing, but a lot of functionality is also relying on backend processes, so that makes it complex.
In all honesty, but personally I just can't see performing hard stop/starts and iisreset actions as true workaround to perform forced refreshes of data.
Most caches present in the MongoDB are refreshed in a 4 hrs interval.
The Command Center is indeed under constant development and we can expect all these quirks and features to get polished and enhanced with every new version that is released. It will get to a point where it will become a 1:1 substitute of the Commcell Console.
+19Yes, but imho it's taking way too long. The admin console how it used to be called was introduced in 2016/2017 already.
You can stop the tomcat service from webserver and perform IISRESET from CMD admin mode. Start the tomcat service again and check the status. For reports if it is getting populated with the help of private metrics reporting then try to upload the private metrics manually and check the status again in the dashboard.
Do you know the refresh interval? Because I noticed that from one day to another, the data was refreshed on Command Center.
This is the data:
This data comes from local metrics collection, which gets refreshed once in a day. Dashboard and health reports uses data from metrics collection. To see current usage go to storage pool properties.
As mentioned above, Dashboard and health reports uses data from metrics collection which gets refreshed once in a day. To see current usage go to storage pool properties.
+13Seems to me that Commvault is using their present user base as testing subjects with the lack of sync between Command Center and Console.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
