Enterprise Vault™ Housekeeping for the Monitoring Database
About housekeeping for the Monitoring database
If you do not assign some additional roles and permissions to the Vault Service account before you run the Enterprise Vault Configuration wizard for the first time, the wizard fails to create a SQL purge job for the Monitoring database history records. Upon completion, the Configuration wizard logs an event log error with the category "Monitoring Configuration Utility", and Event ID 41123. The error description begins as follows:
Monitoring Configuration Utility reported error: SQL Error at: --
The error description then lists the contents of a purge job SQL script file.
Without the SQL purge job, the history records for the Monitoring database continue to grow.
This technical note describes:
How to assign to the Vault Service account the roles and permissions that are required to create the purge job. Ideally you should perform these steps before you run the Enterprise Vault Configuration wizard for the first time.
How to manually create the SQL purge job if you did not assign the additional permissions before you ran the Enterprise Vault Configuration wizard for the first time.
Note:
From Enterprise Vault 10.0.3, you can limit the Vault Service account's SQL privileges to increase database security. The Enterprise Vault databases contain a set of roles that enable you to assign to the Vault Service account only those SQL privileges that are required to run Enterprise Vault. However, if you limit the SQL privileges of the Vault Service account for normal daily operations, you may need to grant additional SQL privileges to the account for other tasks that require higher privileges.
For more information on using the SQL Server roles, see the following article on the Veritas Enterprise Support site: https://www.veritas.com/docs/100038151.