Forum Discussion

AKL's avatar
AKL
Level 6
13 years ago

Deletions & Expiry & Discovery Accelarator

Hello Admins

I had few quick questions around Expiry & deletions and how legal holds play with them (well they don't let you delete stuff - but just some insight to it)

Brief background - We're running Enterprise vault 9.0.1.1073 with same version of Discovery accelarator, backend being SQL 2008 R2 farm.

I'll be enabling expiry on EV site such that existing/running journaling archives will be cleared out to a good extent and in future, all archives older than 12 months (user archives) will get expired as well. Now before going out and enabling expiry, I thought it will be safe to install this hotfix, which makes sure that items on legal hold are excluded rather than EV going round & round trying deletions:

http://www.symantec.com/business/support/index?page=content&id=TECH177042

Q1) If I go with content of above tech-note - legal hold & expiry runnign should NOT impact server performance. Right?

Q2) Does above holds true for deletions as well? i.e. if I start going wilder and start marking old orphaned archives for deletion which've items on DA legal hold, it will not impact server performance? (well deletion process will just making sure legal hold will not make it harder on servers)

Q3) There's a histrorical vault store & partition which contains very old data in Environment. There's no journal mailbox or other stuff associated with it. How can I delete/expire items from it such that everything except items on legal hold there are deleted/removed successfully? Like should I mark vault store for deletion completely, which way items on legal hold won't let deletion process complete OR is there a way for applying expirty on historical vault store?

Q4) and again in above scenario IF I mark vault store for deletion - Will legal hold mess up with deletions & server performance?

Sorry if I asked too many questions. Just deletion process is pretty touchy and resource intensive so trying to cover as much grounds as I can.

Thanks in advance !

Basics
Configuring
Enterprise Vault
Information Governance
Troubleshooting
  • GCSPT's avatar
    GCSPT
    13 years ago

    HI AKL

    Not sure where you read the "should NOT impact server performance" part, but this HF will make deletions much less resource intensive. Storage Expiry as I am sure you can imagine will take some resource but if your system is specked properely there should be no adverse affects.

    As far as I am aware on 9.x if an object (archive data or an archive) has been searched on or touched by a CA/DA search then that object will be logged in the vault interest table which will then stop the full deletion of that object, until it is cleared from the Accelerator application. Normally by means of succesful deletion of the Case/Dept.

    So to kind of answer yru 4 questions as much as I think I can. There will be a resource overhead on storage expiry as wtih any activity that a server processes, it is relative to the amount of data being removed/deleted. The data that expriy or your wilder deletions tries to remove should be restricted to those objects that have no interest in any DA/CA Case or Dept and that interest involves the likes of merely being searched even if it is not exported or reviewed. That hook should only be released when the Accelerator application removes the object that has the interest in that item.

    For example: User1Archive with User1archiveemail are older that 5 years, that comes in line with the expiry policy. That item also contained a hotword that was used in a DA search and so the archive and that item with the hotword is placed in the DA Cusotmer database and kept there until the Case has been deleted. That item should not be expired even though it applies to the storage expiry policy until that case has been deleted.

     

    Hope that makes some sense.

  • GCSPT's avatar
    GCSPT
    Level 5
    13 years ago

    HI AKL

    Not sure where you read the "should NOT impact server performance" part, but this HF will make deletions much less resource intensive. Storage Expiry as I am sure you can imagine will take some resource but if your system is specked properely there should be no adverse affects.

    As far as I am aware on 9.x if an object (archive data or an archive) has been searched on or touched by a CA/DA search then that object will be logged in the vault interest table which will then stop the full deletion of that object, until it is cleared from the Accelerator application. Normally by means of succesful deletion of the Case/Dept.

    So to kind of answer yru 4 questions as much as I think I can. There will be a resource overhead on storage expiry as wtih any activity that a server processes, it is relative to the amount of data being removed/deleted. The data that expriy or your wilder deletions tries to remove should be restricted to those objects that have no interest in any DA/CA Case or Dept and that interest involves the likes of merely being searched even if it is not exported or reviewed. That hook should only be released when the Accelerator application removes the object that has the interest in that item.

    For example: User1Archive with User1archiveemail are older that 5 years, that comes in line with the expiry policy. That item also contained a hotword that was used in a DA search and so the archive and that item with the hotword is placed in the DA Cusotmer database and kept there until the Case has been deleted. That item should not be expired even though it applies to the storage expiry policy until that case has been deleted.

     

    Hope that makes some sense.

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Thanks for detailed info GCox, above makes perfect sense.

    Quick question - If an item is NOT on legal hold as per DA but has a case open for it - The item still remains in VaultInterest Table?

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Hello - Just following up on confirmation around vault interest table question. I might've been in wrong boat thinking only DA legal hold items in the VI table - Are all items associated with any DA case in vault interest table?

  • JesusWept3's avatar
    JesusWept3
    Level 6
    13 years ago

    The only thing that will go in to the Vault Interest table are archives that are being searched.

    Items that are discovered are only in the DA database
    Items that are on legal hold are in the HoldSaveset table of the Vault Store database
    Archives that have been searched are in the VaultInterest table of the Directory database.

    The VaultInterest entries can be manually removed from the VAC in 10 SP1+ only
    The only other way for them to be removed is to delete the case from DA then the interest is removed, otherwise if a case is open, accepted, closed etc, the archives will still remain

    The only thing that will stop items from being deleted is either a legal hold or the retention category being put on a hold, if an archive is in the VaultInterest table, items can still be deleted, and if you try to delete the entire archive itself, it will delete the contents then every time storage starts up, you will get an error saying that the archive could not be deleted because of a Foreign Key Constrain in the VaultInterest table

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Thanks for the detailed description and assistance guys. This surely gives me more clearer picture and will help in planning the expiry & deletions accordingly.