Enterprise Vault may not remove all fingerprints or storage entries during a rollback operation (failed storage attempt)
|Article:TECH126173|||||Created: 2010-01-02|||||Updated: 2014-10-08|||||Article URL http://www.symantec.com/docs/TECH126173|
Enterprise Vault 8.x introduced an advanced Single Instance Storage mechanism to further reduce the footprint of physical storage required for archived items by creating and storing a unique fingerprint within a new database. Under certain conditions, a SQL deadlock can occur during the creation of these fingerprints, causing orphaned fingerprints (that cannot currently be removed) to exist within the database. Changes have been made in Enterprise Vault 8.0 Service Pack 2 to reduce the likelihood of SQL deadlocks that could result in orphan records being created as well as code changes to mitigate any errors stemming from such deadlocks.
At no time could a data loss situation occur due to the orphaned fingerprints.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.
CSavesetSISManager::RollbackSIS does not appear to be removing all fingerprints or storage entries during a rollback
Article URL http://www.symantec.com/docs/TECH126173