Quantcast
Channel: Symantec Connect - Archiving and eDiscovery - Discussions
Viewing all articles
Browse latest Browse all 3821

Is there a way to identify which archives have items that are part of a DA case/research folder?

$
0
0
Oui, j'ai besoin d'une solution

Often people will want to delete mailbox archives they don't need any more, especially archives whose corresponding AD account is deleted.

I noticed today on a DA server that we were getting lots of these warnings:

 

---------------

Log Name:      Symantec Enterprise Vault
Source:        Accelerator Service Processor
Date:          7/31/2013 2:18:51 PM
Event ID:      480
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EVDAComputer
Description:
APP AT - Customer ID: 4 - Archive '18FD793D8D0E3B847971845B8D4E5309D1110000EVxxxx' failed to registered error code: -1073472711
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Accelerator Service Processor " />
    <EventID Qualifiers="0">480</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-31T18:18:51.000000000Z" />
    <EventRecordID>161121</EventRecordID>
    <Channel>Symantec Enterprise Vault</Channel>
    <Computer>EVLEGAL1.admin.bcps.k12.md.us</Computer>
    <Security />
  </System>
  <EventData>
    <Data>APP AT - Customer ID: 4 - Archive '18FD793D8D0E3B847971845B8D4E5309D1110000EVxxxx' failed to registered error code: -1073472711</Data>
  </EventData>
</Event>

 

---------------

 

Searching in the console for that archive ID turned up nothing, but we could find the user name in the DA database connected to that archive ID.  I suspect that if you delete an archive while DA is referencing items in a case or research folder will cause that warning to happen.

I would like to be able to know before deleting an archive if DA is using any of the items in it.  Sometimes we're dealing with hundreds of cases, so looking at each case individually wouldn't work.  Any other way to know?


Viewing all articles
Browse latest Browse all 3821

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>