Overview
Endpoint devices such as laptops and desktops often store valuable business data, including:
User documents
Spreadsheets and presentations
Project artifacts
Application exports
Offline email archives
Temporary working files
Data stored only on endpoints presents several operational risks, including:
Device theft or loss
Ransomware infection
Hardware failure
Accidental deletion
Lack of centralized governance
To ensure structured archival into Vaultastic, the recommended approach is:
Synchronize endpoint data to a cloud drive platform.
Use LegacyFlo to periodically archive the data into Vaultastic.
Supported cloud drive platforms include:
Microsoft OneDrive
Google Drive
This architecture leverages existing enterprise cloud storage infrastructure while enabling centralized archival and governance.
Vaultastic Storage Targets
Endpoint data is typically archived into the following Vaultastic storage tiers.
| Store | Use Case |
|---|---|
| Open Store | Medium-term archival with searchable access |
| Deep Store | Long-term archival optimized for low-cost storage |
The appropriate store depends on:
Expected access frequency
Regulatory retention duration
Cost considerations
Supervision requirements
Endpoint Archival Architecture
The recommended architecture uses cloud drive synchronization as an intermediate layer.
Typical data flow:
Endpoint files are synchronized to OneDrive or Google Drive using desktop sync clients.
Files are stored in the user’s cloud drive account.
LegacyFlo periodically copies selected folders into Vaultastic.
Retention policies in the cloud drive manage storage limits.
This approach avoids deploying backup agents on endpoints and relies instead on existing cloud synchronization infrastructure.
Why Use Cloud Drive as an Intermediate Layer
Operational Simplicity
Cloud drive sync clients are already widely deployed in enterprise environments and are typically managed centrally through administrative consoles.
This removes the need to deploy or maintain dedicated endpoint backup agents.
Reduced Endpoint Complexity
Endpoint devices:
Synchronize files automatically in the background
Require minimal user configuration
Remain protected even when operating outside the corporate network
All archival logic resides in LegacyFlo, rather than on the endpoint itself.
Centralized Governance
Cloud drive platforms provide centralized management features such as:
Administrative visibility
Access controls
Retention configuration
Audit logging
These capabilities help enforce governance before data is archived to Vaultastic.
LegacyFlo Archival Process
LegacyFlo connects to the cloud drive platform and transfers selected data into Vaultastic.
Typical process:
LegacyFlo connects to OneDrive or Google Drive APIs.
Selected folders are enumerated.
Files are copied to Vaultastic Open Store or Deep Store.
Indexing and retention policies are applied.
Supported ingestion scenarios include:
Entire user drive archival
Selected folder archival
Date-based filtering
Scheduled incremental jobs
Archival jobs may be configured as:
One-time historical ingestion
Scheduled recurring synchronization
Managing Retention in Cloud Drives
Retention policies should be configured in the cloud drive platform to prevent storage quota exhaustion.
Typical approach:
Files are archived to Vaultastic after a defined period.
Cloud drive retention policies remove files after archival.
Vaultastic maintains long-term retention independently.
Example policy:
| Stage | Action |
|---|---|
| After 90 days | Files copied to Vaultastic |
| After 120 days | Files removed from cloud drive |
| Long-term | Files retained in Vaultastic |
This ensures:
Cloud drive storage quotas remain controlled
Endpoint backup remains continuous
Long-term data retention is preserved
Initial Configuration
Follow these steps to implement endpoint archival.
1. Enable Endpoint Synchronization
Deploy the OneDrive or Google Drive sync client to endpoint devices.
Define which folders should be synchronized and confirm that files are successfully uploaded to the cloud drive.
2. Define Archival Scope
Identify the folders that should be archived.
Determine:
Retention requirements
Target Vaultastic storage tier
Archival frequency
3. Configure LegacyFlo Ingestion
Register the required API credentials.
Define:
User accounts or folder paths
Destination Vaultastic store
Filtering rules (if applicable)
Configure the archival schedule.
4. Configure Cloud Drive Retention Policies
Define lifecycle rules to manage storage limits.
Ensure that deletion policies only apply after data has been successfully archived to Vaultastic.
5. Validate End-to-End Workflow
Test the complete workflow:
Upload a test file to an endpoint.
Verify synchronization to the cloud drive.
Confirm LegacyFlo ingestion into Vaultastic.
Validate search and retrieval functionality.
Confirm retention enforcement.
Recommended Implementation Sequence
A typical deployment follows this sequence:
Deploy and validate endpoint cloud drive synchronization.
Define archival scope and retention model.
Configure LegacyFlo ingestion jobs.
Perform initial historical ingestion.
Enable recurring incremental synchronization.
Apply and validate cloud drive retention policies.
Monitor ingestion logs and storage metrics.
Benefits of Endpoint Archival in Vaultastic
Archiving endpoint data using cloud drive synchronization and Vaultastic provides:
Protection against device loss and ransomware
Centralized compliance-ready retention
Reduced reliance on endpoint backup agents
Controlled cloud storage growth
Durable, searchable long-term preservation
By combining cloud drive synchronization with LegacyFlo ingestion into Vaultastic, organizations establish a scalable endpoint archival framework aligned with governance and compliance requirements.