Overview
The Open and Deep Stores support structured operations on archive file formats including:
.pst
.zip
.csv (content list files)
These capabilities allow you to:
View metadata
Extract selected content
Generate content lists
Move email data to Active Store
Convert archive formats
1. Understanding Content List (.csv) Files
When data is uploaded using LegacyFlo, a corresponding .csv content list file is usually created.
The CSV file contains:
Email metadata:
Date
Sender (From)
Recipient (To)
Subject
File metadata (for drive archives)
Supported Operations:
View contents using the eye icon
Search within metadata fields
Select and extract specific items
Notes
- The
.csvfile is required for performing selective extraction. - If a
.csvfile is not available; it must be generated before proceeding
2. Working with PST Files (.pst)
PST files typically contain mailbox archives.
Available operations
- Generate content list
- View metadata
- Extract selected emails
- Move content to Active Store
A. Generate Content List
If the PST file was not processed via LegacyFlo:
- Select the PST file.
- Click Generate Content List.
- A LegacyFlo job creates a corresponding
.csvmetadata file.
Output
- A
.csvfile is created and linked to the PST file.
B. View and Extract Email
Open the associated .csv file.
Search by:
Date
From ID
To ID
Subject
Select required emails.
Click Extract.
Choose output format:
PST
EML (ZIP)
Submit request.
Output
- Extraction is processed as a LegacyFlo job.
- Notifications are sent on job start and completion.
C. Move PST Content to Active Store
If full keyword-level search is required:
Select the PST file.
Click Move to Active.
Submit LegacyFlo request.
Output
- Emails are indexed in Active Store.
- Full search capabilities become available.
Best Practice:
Create a temporary vault for investigation. Delete the vault after use.
Note
- Movement is a bulk operation. Individual email selection is not supported in this step.
3. Working with ZIP Files Containing EML Files
Available operations:
Generate content list
View metadata
Extract selected email
Move to Active Store
Convert to PST
Process
- Same workflow as PST files:
- Generate
.csv - Search metadata
- Extract or move data
- Generate
4. Working with ZIP Files Containing Other Documents
When ZIP files contain non-email documents:
Available operations:
Generate content list
View file metadata
Extract selected files
Notes
- Email-specific operations (e.g., move to Active Store, convert to PST) are not supported for non-email content.
- Only metadata-level operations and extraction are available.
5. Restoring PST/ZIP Files in Deep Store
If the archive is in Deep Store:
Restore the file first.
Wait for restoration completion.
Perform content viewing, extraction, or movement.
Important
- No operations are available until restoration is complete.
- Restoration time depends on file size and storage tier.
6. Tracking Extraction and Movement Jobs
All long-running operations generate a LegacyFlo request.
To track a job
- Record the Request ID
- Go to LegacyFlo Requests Dashboard
- Monitor status:
- Submitted
- In Progress
- Completed
- Failed
Notifications
- Email notifications are sent for:
- Job start
- Job completion
- Failures (if any)
7. Output and Download Locations
Extraction Outputs
- Extracted files are made available for download after job completion.
- Output format depends on selection:
- PST → single archive file
- EML (ZIP) → compressed file
Access
- Download links are provided in:
- Email notification
- LegacyFlo Requests Dashboard
8. Permissions and Access Control
Required permissions
Users must have:
- Access to Open/Deep Store
- Permission to:
- View files
- Generate content lists
- Extract content
- Move data to Active Store
Notes
- Operations may be restricted based on role.
- Unauthorized actions will not be visible in UI.
9. Limitations and Constraints
- Operations require a
.csvcontent list. - Deep Store files must be restored before use.
- Large files may result in longer processing times.
- Partial extraction depends on metadata availability.
- Conversion is supported only for email-based archives.
10. Error Handling and Failure Scenarios
Common failure scenarios
- Missing
.csvfile - Corrupt PST/ZIP file
- Unsupported file format inside ZIP
- Interrupted LegacyFlo job
Resolution steps
- Verify file integrity.
- Regenerate content list.
- Re-submit the request.
- Check job logs in the LegacyFlo dashboard.
Summary
Structured file handling in Vaultastic enables:
Metadata-level inspection
Selective extraction
Movement to Active Store for keyword search
Format conversion (ZIP to PST)
Controlled investigation workflows
For basic file upload and management, refer to the: