1 Archive with 1 item under legal hold
Created: 07 Jan 2013 | Updated: 07 Jan 2013 | 11 comments
This issue has been solved. See solution.
This is an EV 9.0.2 environment, single server running on Windows 2003.
At some point DA was used to do some test searches and legal hold was enabled.
Decided to perform intra-site archive moves to get archives to new vault stores on newer server so the Legal Holds were removed from the one and only case.
Post archive move a single source archive reported through Event Viewer that it could not be deleted due to items being on hold.
Question is this:
If DA had only a single case visible in the console and the associated Legal Hold was removed and then the case was deleted....why does an archive still report having an item on hold?
Is there a way to remove this so I can delete the storage it is on and finish decommissioning the source server?
Discussion Filed Under:
Comments 11 Comments • Jump to latest comment
can you run this against your DA customer databases and see if it returns any results?
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
also look at the table in your vault store DB called "HoldSaveset"
This will show you all of the savesets on hold, and also the ArchivePointIdentity associated with each saveset.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
The query executes successfully but produces 0 results.
If you do a select * from holdsaveset against the vault store database do you get results there? (That is the second question Andy was asking about.)
You might have to delete the entries from there. It could be when the case was deleted the hold wasn't lifted. I seem to remember an issue in the older versions that when that happened it didn't clean up holdsaveset correctly.
Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK
Tony - I executed the query and the results are zero.
AndrewB - here is the output from HoldSaveSet...although I'm not sure what to do with the info :)
HoldIdentity 9
SavesetIdentity 123385
HoldDataIdentity 2
HoldGroupIdentity 2
ArchivePointIdentity 1
i believe you just want to delete that entry. i recommend to backup the db before you make any changes.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
This is the exact error from the Event Viewer Enterprise Vault log...
So how did you get results
if select * from holdsaveset had no results??
Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK
Tony - my error the results you're asking about came from the query to HoldSaveSets. Prior to that Andrew asked for the results from a query to SearchResults which came back 0.
I confused the two as I was typing my response.
Ah ok, you will just need to clear the entry out of the HoldSaveSets table and you should be good to go.
Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK
Removing that remaining row from the HoldSaveSets table got rid of the problem.
thanks AndrewB and Tony!
Couldn't mark you both as the solution so had to give it to Andrew since he was first in..
Would you like to reply?
Login or Register to post your comment.