Download and run the load report and the balance workflow:

https://documentation.commvault.com/2022e/essential/100883_index_server_load_overview.html

Haha, CommVault is punking me.  Index State report:  MULTIPLE CRITICAL ISSUES.

Index Load report:  No worries bro, 100% good.

I believe they are reporting on different things.  One is per subclient, the other per Media Agent (load balancing, etc.).

Can you click on the Critical items and see the reasons stated?

None of the fields in the Index State report are clickable links.

Ken

That’s definitely not helpful then.  Can you create an incident requesting a) clarity and b) a CMR to add more contextual help to the report?

Share the case number here once you do.

Hi Ken - we may need a ticket - the remarks column should show the reason but its showing as N/A for some reason. My guess is that those ones marked critical have not had a backup in 30 days. 

can you confirm that?

https://documentation.commvault.com/2022e/expert/10784_index_backup_operations_indexing_version_2.html

@Mike Struening is right, the media agent and subclient/backupset perspective are two completely different things.
Your issue lies on subclient/backupset level index backups, I would check with support to be sure whats happening here.

Unfortunately I didn’t keep a screen capture that showed the client names so I can’t be 100% certain but it is very unlikely that any of my servers would have gone 30 days without a backup.  Also unfortunate is that when I navigate to Health Report > Index State, all 65 entries now show as Good.

Fortunately for me but unfortunately for this conversation, when I navigate to Health Report > Index State, there are no longer any entries in a Critical status.  All 65 clients on that report show as “Good” so I’m no longer in a position to open a ticket to investigate the “critical” entries. 

Do you think I should open a ticket to get more clarity added to the documentation (https://documentation.commvault.com/2022e/essential/38739_health_report_index_state.html)?  To be honest I’m not familiar with the acronym “CMR”.

Ken

CMR=Customer Modification Request.

Essentially, any product enhancement you want to see, create a support case and state your request.

The engineer who takes the case will message the right dev team to see if this fits in our product timeline, and if so, accept a CMR for your idea.

Once you create the case, let me know the number and I’ll track it.

CommVault incident 220822-737 has been opened asking that additional information on how to indestigate and resolve non-”Good” statuses be added to the Index State documentation (https://documentation.commvault.com/2022e/essential/38739_health_report_index_state.html).

Ken

Thanks!  I’ll track it.

From the Health dashboard, if the Index State tile is reporting any issues, the Remarks section will change from "Meets Expectation" to "How to troubleshoot Index Issues for more information"

https://documentation.commvault.com/2022e/essential/38689_health_report_index_state_tile.html

This phrase will link through to the following documentation page:

https://documentation.commvault.com/v11/expert/10756_reports_indexing_version_2.html

This page includes information useful in resolving the errors you may see in the report. 

You can extract additional information about the Indexes with issue by revealing additional non-default columns in the Index State report - these will assist with the troubleshooting process.