cancel
Showing results for 
Search instead for 
Did you mean: 

adding archives to legal hold on discovery accelerator

alv
Level 3

our legal dept wants to place 300 or so archives on legal hold, meaning they want to prohibit any deletion within those archives. at the same time they would like to be able to add and remove archives from this group. is discovery accelerator the best way to do this? if i create a case and add all 300 archives, along with a recurring daily search to all items to legal hold and auto accept, would that work? how would i remove items that were already accepted for an archive that was removed? also, if items are on legal hold through discovery accelerator, can the archive be deleted from the vac? running: ev8 sp4 thanks in advance, alv

1 ACCEPTED SOLUTION

Accepted Solutions

Damon_Kaswell
Level 4
Employee
Hi alv,

Scheduled searches aren't the best method for preventing deletions from an archive, because there will still be a gap between searches during which new items can be deleted. Preventing the deletion of any messages in an archive is best done from within the VAC itself, either in the properties of the archive or at the Site level (if you want to prevent all deletions in the entire environment). While you could technically set up the search/auto accept scenario you describe, it would be easy for a user to circumvent, and would also create so much SQL traffic it would become prohibitively difficult to maintain your SQL server.

As for deleting an archive from the VAC, that can't be done as long as there are any items in the archive that are on hold, haven't been backed up, or for any other reason can't be deleted.

View solution in original post

2 REPLIES 2

Damon_Kaswell
Level 4
Employee
Hi alv,

Scheduled searches aren't the best method for preventing deletions from an archive, because there will still be a gap between searches during which new items can be deleted. Preventing the deletion of any messages in an archive is best done from within the VAC itself, either in the properties of the archive or at the Site level (if you want to prevent all deletions in the entire environment). While you could technically set up the search/auto accept scenario you describe, it would be easy for a user to circumvent, and would also create so much SQL traffic it would become prohibitively difficult to maintain your SQL server.

As for deleting an archive from the VAC, that can't be done as long as there are any items in the archive that are on hold, haven't been backed up, or for any other reason can't be deleted.

alv
Level 3

thanks damon.  i'll go with the vac approach.