MithiDocs

Vaultastic Active Store Data Management

Uploading Data to the Active Store

Depending on the Data Source, differet methods can be used to upload communication data to the Vaultastic Active Store.

Data SourceMethod
Live Mail flow Journaling or forwarding configuration on the source system
Application mail flowVaultastic Ingestion API
MailboxVaultastic Data Upload
Teams or Google Chat transcriptsVaultastic Data Upload
Data files such as PST/ZIP/MBOX/Maildir available on S3 bucketsVaultastic Data Upload
Other Vaultastic StoreVaultastic Data Upload
Activation via Open or Deep Applications


Export Data from the Active Store

Retrieving one mail at a time

Single mail can be downloaded or forwarded using the  Active Store eDiscovery view by end users logging into their vaults.

Retrieving mail in bulk

For bulk retrieval, there are three options available

  1. Using the export feature of the eDiscovery interface of Vaultastic 
  2. Using the export function from the Vaultastic Admin Panel
  3. Using LegacyFlo service to extract data to S3


The comparison between these 3 options is as given below:


eDiscovery in VaultasticVaultastic Admin PanelLegacyFlo
Access to the featureAvailable to all users in Vaultastic via the Active Store eDiscovery interfaceAvailable to all domain administrators via Admin panel

Available to the administrators of the organization using Legacyflo VAULTASTIC4-S3-PST or VAULTASTIC4-S3-ZIP requests.

Output formatEML or PST filesEML or PST files

EML in ZIP or PST

Content
  • The search results are exported.
  • Depending on the search, the contents can be across folders.
  • Depending on the user access the content can be across vaults.
  • The contents of a single vault can be exported at a time.
  • To download from multiple vaults, multiple requests will have to be submitted.
  • The content of a single vault is exported with a single LegacyFlo request.  
  • To download from multiple vaults, multiple requests will have to be submitted.
  • Can export entire vault content or narrow down by specifying date range and source folder.
Mail Size LimitsIf the search results contain mail  greater than10MB, they will be skippedNo limits on mail sizeNo limits on mail size
Export size limit

Vaultastic Version 3: 5 GB

Vaultastic Version 4: 50 GB

The export is not allowed if the search result size is more than the max allowed size

50 GB

50 GB
File size limitConfigurable.
If the total export is greater than the max size, multiple  files are created
Configurable.
If the total export is greater than the max size, multiple  files are created
A single file will be created
Access to the exported contentThe links to exported content are shared via email. The links are valid for 7 days.The links to exported content are shared via email. The links are valid for 7 days.The exported content is created in an S3 bucket in your account and can be downloaded using a tool such as S3browser.
Monitoring (For long-running jobs)Not AvailableNot availableAvailable via LegacyFlo interface
PerformanceMediumMediumFast
CostAs per LegacyFlo exportAs per LegacyFlo exportAs per LegacyFlo backup to S3 cost
Best suited forVaultastic end users, wanting to retrieve a few emails found using the eDiscovery interfaceFor admins, who want to export vault contents whose size is less than 50GBFor Admins, wanting to retrieve entire vault contents or a large number of emails.
Approximate speed1GB/hour1 GB/hour1 GB/hr

Deletion of data on the Active Store

  1. The Vaultastic Active Store is immutable and individual emails cannot be deleted from the store. 
  2. For mail ingested through journaling or forward, the Vaultastic Active Store maintains de-duped data for a domain, which means that a single mail from a sender to multiple recipients will be saved as a single copy. This mail is will be visible in all the virtual vaults associated with the mail on the store. To delink a mail from a vault, senior admins with sufficient priviledges can delete the vault. Only when there are no vaults associated with a mail, the mails on the Active Store will get deleted.
  3. For mails injested via LegacyFlo, deleting the vault will delete the mail as there will be no other vault which references the mail.
  4. The lifecycle management automation which runs at the start of every month, copies a month's data for all vaults to open/deep store. In the subsequent month, all data successfully copied to Open or  Deep store is deleted provided no vaults with Legal Hold set are still referncing the mail.