Software / Cloud migration
DataTube
Move large datasets between cloud providers and verify what arrived. DataTube supports interrupted transfers and helps your team reconcile the destination with the source.
Platforms and licensing
Supported platforms
Confirm the current application package, supported runtime and provider connections before arranging access.
Licensing
Request the current distribution and licence terms. Confirm any support, hosting or provider charges separately.
Development and support
Developed, supported and owned by Global Digital Forensics.
The product
What DataTube does
Cloud migrations can be interrupted by a dropped connection, a changed object or rejected metadata. The transfer record needs to show what completed and where to resume.
DataTube is built for cloud-to-cloud transfer at large scale. It recovers from interrupted work, compares source and target throughout the migration and maintains an audit trail so the team can identify exceptions and verify completion.
Cloud-to-cloud transfer
Move supported data directly between authorized cloud providers without routing every object through a user's workstation.
Large data sets
Manage long-running transfers and high object counts through a workflow designed for multi-terabyte projects.
Self-recovery
Resume interrupted work from recorded progress instead of restarting the entire transfer.
Continuous verification
Compare source and target state during the migration and identify mismatches that require attention.
Exception handling
Separate failed or changed items for review, retry or documented disposition.
Audit trail
Record transfer activity, verification results and exceptions for technical and client review.
Methodology
Typical workflow
-
Map
Confirm source, target, credentials, data scope, metadata requirements and provider limits.
-
Transfer
Move data in controlled work units while recording progress and provider responses.
-
Recover
Resume interrupted items and isolate exceptions without discarding completed work.
-
Verify
Reconcile source and target, document unresolved differences and produce the migration record.
Operating note
Compatibility and limits
Achievable speed and metadata fidelity depend on provider APIs, rate limits, object characteristics, network conditions and the permissions available at both ends.
Related software and services
Arrange access and define migration acceptance
Request distribution, licence terms, supported provider connections, installation requirements and support arrangements from the product team before planning the migration.
- Source and target: identify provider, object or file types, versions, permissions, account quotas and metadata that must survive the move.
- Credentials: agree limited access, expiry, revocation and where secrets are held; do not put keys in an ordinary inquiry.
- Resume: define checkpoints and how changed, overwritten, failed or deleted source objects are treated.
- Acceptance: compare agreed object counts, sizes, hashes where comparable, metadata and unresolved exceptions. Keep a dated manifest from both ends.
An illustrative manifest can show an object copied successfully while its access-control metadata failed. That item is an exception until it is corrected or explicitly accepted. A completed byte transfer alone does not prove metadata, versions and permissions match.
Talk with an examiner
Discuss this product for your engagement
Tell us the workflow and scale. We can discuss current availability, supported workflows and how it fits an examination or matter.
Since 1992 · 24/7 dispatch · Court-tested experts
Talk with an examiner
Discuss the matter and the next step.
Call to discuss timing, scope and the safest way to share information. Do not send evidence or credentials by email.
24/7 hotline: 1-800-868-8189