Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Any way to accelerate deletions of archives??

Created: 11 Oct 2013 | 7 comments

I know it's not officially supported, but there's a lot of discussion about deleting archives in bulk by setting the ArchiveStatus to 4, and letting the Storage service delete the archives.

I have probably 11000 archives which are abandoned, and I have no requirement for compliance, etc, and would like to delete them.  I deleted a sample of about 280 archives (identified by SQL query, and by setting the ArchiveStatus to 4) and it is working, but 3 weeks later, I still have 120 archives waiting to be deleted.  At this rate, I almost literally will NEVER be able to complete the deletion of 11000 archives.

I'm hoping that someone knows a way to either tell storage service to dedicate more threads, or can tell me how this is being throttled, nad how to speed it up.  There doesn't seem to be any bottleneck on network, server, or disk performance, so I have to believe it's a thread related issue.

Any help would be GREATLY appreciated!!

-Steve

Operating Systems:

Comments 7 CommentsJump to latest comment

Rob.Wilcox's picture

Currently the only Symantec supported way is manually deleting via the VAC.

The SQL way works, yep.. but it will still take a while, because you see EV has to effectively 'unarchive' everything, dereference archived item counts and ... basically a ton of work. It's not just delete 1 row in SQL :)

 

Sorry

172pilot-68's picture

Thanks for the quick response.. 

So - I know the answer is "it depends", but is it reasonalble to expect maybe 1-5 archives per day to be the max I can process?  I have archives across 3 separate EV servers, so I assume that the storage service on all three servers could be working in parallel?  And, just in an attempt to understand the process better:

Is there any way to see what archive the process is working on at any particular time?

I assume that when it's deleting an archive then, it presumably could be un-cabing the files, and then re-cabbing those files that aren't deleted?

I assume the process stops when we go into backup mode?  If so, does it continue where it left off, or does it have to restart something from scratch?  And, based on that, is there anything we can do in our environment to make the deletions complete faster? 

We literally have more turnover in our organization than we are able to process these deletes for, so this is quite critical to us - If it means installing another server, or some other upgrade to help our situation, I'd love to hear what we can do..

I found another article (https://www-secure.symantec.com/connect/forums/sql-query-delete-ev-archive-or-change-archivingstate-mbxarchivingstate-1-mbxarchivingstate-4) that says that overloading the database with too many "4" deletes at once can slow down the situation.  This seems unlikely to me. I would assume that no matter how many archives are marked "4", I assume that they are handled sequentially, but if there's reason to believe that this article is correct, I'd like to understand the process better so I can understand the logic I can use to streamline our process!

Thanks a LOT!!

-Steve

Rob.Wilcox's picture

This might help:

http://thingsilearnedtoday.net/2013/08/30/deleting-an-enterprise-vault-archive/

 

You can adapt the query to monitor the deletions, and again, the number per day = it depends ;-) (on size and so on)

GabeV's picture

Hi,

Deleting an archive is a single thread process. You can dtrace StorageDelete and see which archive is being processed. With three EV servers, assuming that each server has a storage service that handles its own Vault Store, you might be deleting three archives in parallel. Of course, since this operation needs to pull information from SQL, delete data from storage, etc, take a look at the SQL fragmentation and make sure it's under control. Also, it depends of how much data you have on each archive.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

GertjanA's picture

Hello,
How many active archives do you have?
You might be better of in setting up a new environment, move your active archives there (archiveshuttle!!!), then just trash the old environment.
Or try exporting the orphaned archives to pst with the option to remove exported item from archive.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision

GabeV's picture

Hi,

Do you have any updates on this thread? Do you need more assistance regarding this topic? If not, please mark the post that best solves your problem as the answer to this thread.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill