DTrace for MonitoringAgent shows errors for each 5 affected counters as below:
System.InvalidOperationException: Could not locate Performance Counter with specified category name 'Enterprise Vault::Vault Stores', counter name 'JournalArchive Table Size'.
System.InvalidOperationException: Could not locate Performance Counter with specified category name 'Enterprise Vault::Vault Stores', counter name 'JournalDelete Table Size'.
System.InvalidOperationException: Could not locate Performance Counter with specified category name 'Enterprise Vault::Vault Stores', counter name 'JournalRestore Table Size'.
System.InvalidOperationException: Could not locate Performance Counter with specified category name 'Enterprise Vault::Vault Stores', counter name 'Vault Store DB Backup'.
System.InvalidOperationException: Could not locate Performance Counter with specified category name 'Enterprise Vault::Vault Stores', counter name 'Vault Store DB Log Backup'.
The name of these 5 counters had been changed at Enterprise Vault 10.0.2, but Monitoring function still try to read these counters by old names.
Permanent Solution
This issue has been addressed in the following release:
Enterprise Vault 11.0.0 Cumulative Hotfix 3 Release
https://www.veritas.com/docs/000024104
Enterprise Vault 11.0.1 Cumulative Hotfix 1 Release
https://www.veritas.com/docs/000024613
Enterprise Vault 12
The following link contains information about Enterprise Vault 12
https://www.veritas.com/docs/000099905
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products
Important Note: If the temporary workaround SQL explained below has been applied to the environment, rollback SQL MUST BE APPLIED before applying permanent solution. (For more information about the rollback SQL, see Temporary Workaround section below).
Temporary Workaround
As a temporary workaround, Enterprise Vault Administrator can use this SQL.
This SQL updates the CounterName in PerformanceCounterMaster table.
UPDATE
[EnterpriseVaultMonitoring].[dbo].[PerformanceCounterMaster]
SET
[CounterName] =
CASE [PerformanceCounterID]
WHEN 4 THEN 'Journal archive table size'
WHEN 5 THEN 'Journal delete table size'
WHEN 6 THEN 'Journal restore table size'
WHEN 7 THEN 'Vault Store DB back-up'
WHEN 9 THEN 'Vault Store DB log back-up'
END
WHERE
[PerformanceCounterID]
IN
(
SELECT
[PerformanceCounterID]
FROM
[EnterpriseVaultMonitoring].[dbo].[PerformanceCounterMaster]
WHERE
([PerformanceCounterID] = 4 AND [CounterName] = 'JournalArchive Table Size') OR
([PerformanceCounterID] = 5 AND [CounterName] = 'JournalDelete Table Size') OR
([PerformanceCounterID] = 6 AND [CounterName] = 'JournalRestore Table Size') OR
([PerformanceCounterID] = 7 AND [CounterName] = 'Vault Store DB Backup') OR
([PerformanceCounterID] = 9 AND [CounterName] = 'Vault Store DB Log Backup')
)
Use this SQL to rollback.
Important Note: This rollback SQL MUST BE APPLIED before applying permanent solution. (For more information about permanent solution, see above Permanent Solution section).
UPDATE
[EnterpriseVaultMonitoring].[dbo].[PerformanceCounterMaster]
SET
[CounterName] =
CASE [PerformanceCounterID]
WHEN 4 THEN 'JournalArchive Table Size'
WHEN 5 THEN 'JournalDelete Table Size'
WHEN 6 THEN 'JournalRestore Table Size'
WHEN 7 THEN 'Vault Store DB Backup'
WHEN 9 THEN 'Vault Store DB Log Backup'
END
WHERE
[PerformanceCounterID]
IN
(
SELECT
[PerformanceCounterID]
FROM
[EnterpriseVaultMonitoring].[dbo].[PerformanceCounterMaster]
WHERE
([PerformanceCounterID] = 4 AND [CounterName] = 'Journal archive table size') OR
([PerformanceCounterID] = 5 AND [CounterName] = 'Journal delete table size') OR
([PerformanceCounterID] = 6 AND [CounterName] = 'Journal restore table size') OR
([PerformanceCounterID] = 7 AND [CounterName] = 'Vault Store DB back-up') OR
([PerformanceCounterID] = 9 AND [CounterName] = 'Vault Store DB log back-up')
)