Green Bar
Renew Data Logo RenewData Blog Search
Advanced Search

Navigation Divider
Why RenewData
Navigation Divider
Legal Expertise
Navigation Divider
Technology
Hash Values
> De-Duplication Process
Tape Restore vs. Extraction

Navigation Divider
Cost Management
Navigation Divider
Client Success Stories
Navigation Divider
Industry Affiliations
Navigation Divider
Facility Security
Navigation Divider


ActiveVault De-duplication Process

De-duplication is the process of removing forensically identical copies of email messages or files from the production set. Other vendors in the industry must perform de-duplication as a separate process because they do not utilize a single-instance storage model in their systems. Because RenewData already stores de-duplicated data within ActiveVault, there is no additional de-duplication that is necessary upon output. Instead, ActiveVault sometimes must repopulate email files with messages or directories with user files in order to meet client "de-duplication" requirements.

RenewData's standard production output repopulation options are:

Full Repopulation (equivalent to no de-duplication)

  • Native Email: The email file includes all messages for the target user including duplicate messages in all locations.
  • Native User Files: The user directories contain all files for the target user including duplicate files in all locations. Single-Instance Repopulation Within Target User (equivalent to within custodian de-duplication)
  • Native Email: The email file includes one instance of each message in the folder by alphabetical sort order where it resides. Therefore, if message #1 resides in two folders, Folder A and Folder B, then one output, message #1 will be included in the email file only in Folder A.
  • Native User Files: The user directories contain only one instance of each file across all locations

Single-Instance Repopulation Within Target User (equivalent to within custodian de-duplication)

  • Native Email: The email file includes one instance of each message in the folder by alphabetical sort order where it resides. Therefore, if message #1 resides in two folders, Folder A and Folder B, then one output, message #1 will be included in the email file only in Folder A.
  • Native User Files: The user directories contain only one instance of each file across all locations.

Single-Instance Repopulation Within Folders or Directories within Target User (equivalent to within custodian de-duplication)

  • Native Email: The email file includes one instance of each message in any folder where it resides. Therefore, if message #1 resides in two folders, Folder A and Folder B, then one instance of message #1 will be included in the email file in each respective folder.
  • Native User Files: The user directories contain only one instance of each file in each respective directory. Global Single-Instance Repopulation (equivalent to global de-duplication)
  • Native Email: Only one instance of each message will reside across all target users.
  • Native User Files: Only one instance of each user file will reside across all target users.

Global Single-Instance Repopulation (equivalent to global de-duplication)

  • Native Email: Only one instance of each message will reside across all target users.
  • Native User Files: Only one instance of each user file will reside across all target users.



Related Information