Performance counters for "Enterprise Vault::VaultStores" table

The Performance Counters for "Enterprise Vault::VaultStores" table displays the following data for each monitored vault store counter instance:

Instance Name	The instance name.
Status	The status of this instance, based on the status indicator thresholds.
Value	The value of this instance when the Monitoring agent last monitored it.
Warning Threshold	The configured warning threshold for this counter.
Critical Threshold	The configured critical threshold for this counter.
Last Updated	The date and time when the Monitoring agent last monitored this data.

For Operations Manager to be able to sample and display the vault store performance counters, monitoring needs to be enabled for the site in the Enterprise Vault Administration Console. If site monitoring is not enabled, the table is not shown. To check whether Site Monitoring is enabled, right-click the Site node in the Administration Console and select Properties. Then, on the Properties dialog, select the Monitoring tab. This tab also specifies the monitoring start time for each counter.

The monitoring of the vault store performance counters begins at the Operations Manager monitoring frequency when the monitoring start time is reached. The start time is specified on the Monitoring tab of the Site Properties dialog box. If you want to monitor the performance counters immediately, change the monitoring start time and restart the Enterprise Vault Admin service.

Table: Monitored vault store performance counters shows the monitored counters and possible consequences of raised values.

Table: Monitored vault store performance counters

Counter description	Counter name	Consequence of raised values
Number of incomplete backup, indexing or replication operations	Journal Archive Table Size	Indicates a possible issue with backup or replication policies, or with the indexing process. If you have chosen the vault store option to remove safety copies immediately after archive, you may suffer a greater data loss in the event of a hardware failure.
Number of incomplete delete operations	Journal Delete Table Size	Indicates that there are many items pending index deletion. A backlog can indicate that there is a problem with the Indexing service.
Number of incomplete restore operations	Journal Restore Table Size	Indicates that a large number of items are waiting to be restored, implying possible problems with the StorageRestore process.
Number of days since the last backup of the vault store database	Vault Store DB Backup	If the vault store database is not backed up periodically, this may result in data loss or, at minimum, extensive operations to restore Enterprise Vault in the event of hardware failures on the SQL server hosting the database.
Space used in the vault store database transaction log (%)	Vault Store DB Log % Used	Indicates how close the SQL server is to increasing the log file's size by the configured increment for this log file.
Number of days since last backup of vault store database transaction log	Vault Store DB Log Backup	If the vault store database log files are not backed up periodically, this may result in data loss or, at minimum, extensive operations to restore Enterprise Vault in the event of hardware failures on the SQL server hosting the database.
Cumulative size of all the log files in the vault store database	Vault Store DB Log Size	The performance of the SQL server may be adversely affected if there is a shortage of disk space where the transaction logs are stored.
Number of Saveset files awaiting backup or replication	Watchfile Table Size	Indicates a possible problem in backup or replication application policies.