09-06-2012 11:33 AM
Can someone clarify what happens when an entry is manually deleted from the vaultinterest table. I have a couple of archives that need to be relocated to another store. I am unable to move or export and delete these archives due to legal holds or the vaultentryid being in the interest tables. I am told the archives are not on legal hold, but that does not mean there are no searches against them to cause the lock if I understand correctly. Case and search deletion are not an option for various reasons. So the question is, what happens if the entry in the vaultinterest table is removed, are there any negative impacts? Does ev, da, or sql choke with errors down the road?
Solved! Go to Solution.
09-06-2012 03:24 PM
09-06-2012 12:00 PM
As far as I understand from an DA point of view, if the Case still exists then everything will hold the archives on legal hold therefore you won't be able to delete any items related to those archives. I wouldn't delete those entries due to them being linked to other tables and columns etc. and it is never a good idea to delete stuff from DBs unless it is the ExchangeMailboxEntry table. If am being honest, I don't know the exact affect as I don't often delete stuff from the DBs. :)
Your best options is to some how close the DA search case and then move the archives and then create a new Case. If you are told they are no longer on legal hold then why can't you close the case? Just curious!
09-06-2012 02:36 PM
09-06-2012 03:24 PM
09-07-2012 11:35 AM
I should have stated earlier the problem was when archiving runs for a couple of accounts it generates eventid error 13360 among others;
"dbo.uspcu_Vault Error: VaultId = "111E93A5678551113A5D6036DD81110000archive" does not exist."
It does this repeatedly to the point it takes ev services offline. DTraces were done and we could not determine the problem even with Symantec supports assist. I believe the final decision prior to was to delete the case to allow the archives to be moved in hopes of solving the problem. We decided against use of the ignore error reghack as well.
Testing we placed an archive on legal hold. We then deleted the vaultid's from the vaultinterest table. Moved the archive to a new store and ran a query confirming JW3 is correct, the archives remain on legal hold. Moving forward in real world we backed up the db and performed the process again on a problem archive. Next ran a run now and no more errors. The only downside from what we can tell will be the user if they use archive explorer will see two archives (old with cutoff date and new). The original archive now closed will remain until the legal holds are removed and the case is closed or better yet deleted.