How to perform a rollover of the Enterprise Vault auditing database.
| Article:TECH35746 | | | Created: 2004-01-25 | | | Updated: 2012-04-23 | | | Article URL http://www.symantec.com/docs/TECH35746 |
Problem
How to perform a rollover of the Enterprise Vault auditing database.
Solution
The auditing database will grow in size, the amount depending on how busy the Enterprise Vault system is and the amount of auditing that has been enabled.
Eventually, it may required to either remove data from the audit database or to create a new database.
Removing data from the database:
Within the "EnterpriseVaultAudit" database, the "AuditTrail" table is the only table that will grow significantly.
Remove the contents of the "AuditTrail" table and then continue to use the same database, as follows:
1. Back up the "EnterpriseVaultAudit" database
2. Click "Start"| "Programs" | "Microsoft SQL Server" | "Query Analyzer".
3. In the left-hand pane, click the "EnterpriseVaultAudit" database as displayed in Figure 1.
Figure 1:
4. Enter one of the following queries as displayed in Figure 2 and 3.
Figure 2:
Figure 3:
| SQL Query | Function |
|---|---|
| Delete * from AuditTrail | Delete removes records from the table one at a time and records each deletion in the transaction log. Delete is much slower than Truncate. |
| Truncate table AuditTrail | Truncate requires less transaction log space and it does not record each deletion. Truncate is much faster than Delete. |
5. Click "Query" then click "Execute"
Creating a new database:
Create a new database and then modify the "EnterpriseVaultAudit" system DSN to point to the new database by following the steps given below:
1. Create the new database as described in "Creating the auditing database" section of this technical note
2. Stop all the Enterprise Vault services
3. Edit the properties of the "EnterpriseVaultAudit" system DSN as described in "Editing the system DSN" section of this technical note.
4. Start the Enterprise Vault services
Each computer on which the auditing is enabled has a limited number of connections that it can make to the auditing database. These connections are reused as needed.
Creating the auditing database:
Follow the steps below to create the auditing database:
1. Click "Start" | "Programs" | "Microsoft SQL Server" | "Enterprise Manager"
2. In the left pane of Enterprise Manager, expand the tree until you view the name of the computer on which you want to create the auditing database. Click the name of that computer.
3. Click "Action", then "New", then "Database"
4. When prompted for the database properties, enter a name for the new database, such as "EnterpriseVaultAudit"
5. Click OK
6. In the left pane of Enterprise Manager, expand the tree until the databases are visible
7. Click the auditing database that you have just created
8. Click "Tools" | "SQL Query Analyzer"
9. In "SQL Query Analyzer", click "File" and then "Open"
10. Select the file "Audit.sql", which is in the Enterprise Vault program folder (usually C:\Program Files\Enterprise Vault)
11. Click "Query" and then "Execute"
Editing the system DSN:
The system DSN must always be called "EnterpriseVaultAudit". The existing system DSN must be edited so that it connects to the new database. To edit the system DSN, stop all the Enterprise Vault services and then do the following on each computer that logs Enterprise Vault audit information:
1. Click "Start" | "Settings" | "Control Panel" | "Administrative Tools" | "Data Sources (ODBC)"
2. In "ODBC Data Source Administrator", click the "System DSN" tab
3. In the list of System Data Sources, click "EnterpriseVaultAudit" and then click "Configure". The Microsoft SQL Server DSN Configuration wizard starts.
4. On the first page, click "Next"
5. On the second page, click "Next"
6. On the third page, under "Change the default database to", select the database that has just been created
7. Click "Next"
8. Click "Finish" to display the summary information
9. Click "Test Data Source" to verify the connection to the database
10. Click "OK"
The Enterprise Vault Services can now be restarted.
|
|
Related Articles
Legacy ID
273274
Article URL http://www.symantec.com/docs/TECH35746
Terms of use for this information are found in Legal Notices
Thank you.