"Fundamentally, information governance is a business process.  In order to lower risks and achieve greater efficiencies through process improvement, electronic discovery will increasingly become tightly integrated with an organization’s information governance policy, procedures, and infrastructure." How the Information Governance Reference Model (IGRM) Complements ARMA International’s Generally Accepted Recordkeeping Principles (GARP®)

This ABA article describes how an organization’s team of in-house attorneys, lead outside counsel, RIM, and IT professionals can be instrumental in guiding discussions with business management to achieve better eDiscovery by implementing a unified Information Governance (IG) program.

...

Quite some time ago on the forums an Enterprise Vault administrator asked what order folders were processed in a users mailbox.  I did a little bit of research on a test mailbox.  The mailbox contents is shown below:

To see what was happening I added a DTRACE filter for the Archiving Task, and put in the filter includes :

Processing msgs in folder

ProcessUserEx

This resulted in the following trace:

Display Filter:

  Include strings:

    Processing msgs in folder

    ProcessUserEx

  No Exclude Strings

-----

Current File Rollover Settings: 100Mb

-----

10013 19:44:16.046 [3696] (ArchiveTask) <4880> EV:H {CArchivingAgent::ProcessUserEx:#17836} Processing mbx [/o=EV Training/ou=First Administrative Group/cn=Recipients/...

Archiving by definition requires a long term commitment from the vendor and the customer. This recent news around Autonomy and products from Mimosa, Zantaz, HP RISS,HP IAP, Iron Mountain, Stratify, Connected, Aungate and other Autonomy archive and E-discovery products is clearly a disruption. These many different archiving solutions that Autonomy/HP had acquired and begun to EOL or migrate toward IDOL create an information management challenge as IT teams need to juggle product EOL's, migrations, retention policies, legal holds and active litigation while moving to IDOL, a platform that has yet to prove it is a longterm solution.

Symantec will be stepping forward with a migration plan for Autonomy customers seeking more stable platform for information management, archiving and E-Discovery.

Symantec’s Enterprise Vault has been the consistent leader in archiving for more than 10 years. We have had our great moments and had a few bumps as well. I've...

I recently had a run-in with FSAUtility trying to recreate an Archive point which got duplicated.

I got confused over what was required for the UNC Path part of the command line.

Tech 64969,  states :-   "run the fsautility -a -s "UNCpathname"    OK so what is required for "UNCpathname"

I assumed "the path to the Archive point" and checked in the manual for the syntax

The Utility manual states:-

FSAUtility -a -s UNC_path [-l log_level] [-r]
Where:
■ -s UNC_pathspecifies the path to the required folder, volume, or
file server.

Sounds reasonable, they want the path to the Archive point foder.

I then spent hours running this command line, and getting "invalid UNC path errors" Researching UNC Path specs and syntax etc.

By chance I accidentally ran FSAUtility without any options and got the command help.