JournalArchive table has grown significantly since upgrading to Enterprise Vault (EV) 8.x or later.
|Article:TECH67576|||||Created: 2009-01-05|||||Updated: 2014-09-15|||||Article URL http://www.symantec.com/docs/TECH67576|
Enterprise Vault 8 introduced a new feature called Transaction history. The Transaction history is used to determine how long to record updates to archives. Updates include adding new items, deleting items and moving items. The update records significantly improve the performance of vault cache synchronization by providing records of the changes to an archive since the last vault cache synchronization. If a user has not synchronized their vault cache within the transaction history period, then Enterprise Vault will process the archive to determine the updates.
The transactions are tracked in the JournalArchive, JournalDelete and JournalUpdate tables which are located in the Vault Store databases. Since the tables will grow larger than they did in previous versions of Enterprise Vault, additional considerations should given to ensure the SQL server does not run out of disk space. Alternatively, the number of days the Transaction history is retained may be modified.
- Right click the Enterprise Vault Site name (first container under Directory on ...) and select Properties.
- For Enterprise Vault 10.x and below, follow these steps:
a. Select the Archive Settings tab.
b. Under the Transaction history section, Retain archive transaction history for: Specify the number of days to retain updates to archives. By default, the data is retained for 32 days.
- For Enterprise Vault 11.x, follow these steps:
a. Select the Advanced tab.
b. Select Storage under List settings from.
c. Select Transaction history from the list and click on Modify.
d. Specify the number of days to retain updates to archives. By default, the data is retained for 32 days:
Article URL http://www.symantec.com/docs/TECH67576