SQL DEADLOCK ENTERPRISE VAULT ARCHIVE
SQL DEADLOCK ENTERPRISE VAULT WINDOWS

SQL DEADLOCK ENTERPRISE VAULT ARCHIVE

Archive being 'Of Interest' via Discovery Accelerator (DA):.Archives which have associated items on legal hold will not be deleted until all items associated with the archive are removed from legal hold and deleted by storage. Items on legal hold cannot be deleted from Enterprise Vault. Archives affected by the factors below will appear to be in a permanent 'Marked for Deletion' status.Įnterprise Vault Discovery Accelerator (DA) has the option to place discovered items on 'Legal Hold'. High fragmentation can cause heavy queries to take longer than expected, cause SQL dead-locks, or fail entirely.īelow are additional components which will stop the deletion of an archive. As per best practices, regular SQL maintenance must be performed against the SQL indexes in order to keep especially large SQL table indexes from becoming fragmented. The saveset entries associated with an archive are referenced within the Vault Store database. The greater number of total items in the storage location, the longer the trawl will take. The storage location must be searched for each item to be deleted. Due to the design of EV, these items are stored by the age or modified date of the email, not by the archive. This process will also be delayed due to the number of Index files and Data files that must be deleted. If there are a large number of items in the Mailbox archive, it will take time to locate and purge these from the database. Size and quantity of items in Vault Store:.

SQL DEADLOCK ENTERPRISE VAULT WINDOWS

Depending on the time windows allowed for nightly backups, deletion requests may be delayed significantly. When Enterprise Vault is in a Backup Mode, items are not updated, inserted or deleted. If there is numerous archive requests, a delete request may be delayed. If a delete request is performed, it will be queued in the same Queue as the archiving requests. It may take time to trawl through the vault store partition(s) to identify all references for a particular archived item.Īspects that may slow down the deletion process:ĭuring the Journal Archiving and Mailbox Archiving process, Updates and Inserts against the EnterpriseVaultDirectory, Vault Store Database(s) and Fingerprint Database occur. The performance of the deletions are dependant on a number of factors, including the total items on the Storage Location (Vault Store). Only after all saveset references and index references are removed, will the actual Archive be deleted. Note: The above process occurs for every item within an Archive. Once the SQL entries for the each of the saveset objects are removed, a delete is performed on the physical data.

Sql deadlock enterprise vault