GDF Software for Verified Cloud to Cloud Migration
Data
A cloud migration that stops partway through and cannot say which objects made it is worse than one that never started. DataTube moves terabyte scale data directly between cloud providers, resumes cleanly after an interruption and reconciles the source against the target object by object. You finish with an audit trail that proves what arrived, which is what auditors, legal teams and the business all ask for.
Platform, Distribution and Ownership
Supported Operating Systems and Platforms
DataTube is a cross platform application built with Python. Confirm the current application package, supported runtime and provider connections before arranging access.
Software Licensing and Deployment Models
Request the current distribution and license terms from GDF. Any support, hosting or provider charges are confirmed separately, so the migration budget holds no surprises.
Engineering Development and Enterprise Support
DataTube is developed, supported and owned by Global Digital Forensics, so the people who answer your migration questions work for the firm that wrote the software.
The initial consultation is free, and a senior examiner sets the plan with you on the first call.
The product
Migrations Break, and the Record Must Not
Cloud migrations are interrupted by dropped connections, objects that change while the copy runs and metadata the destination refuses to accept. The failure itself is ordinary. The damage comes when nobody can say which objects completed, which did not and where a restart should begin, and the team either copies everything again or trusts a destination it cannot verify.
DataTube was built by Global Digital Forensics for cloud to cloud transfer at large scale, by a firm that has handled evidence since 1992 and knows what a verification record has to look like. It recovers from interrupted work without discarding what finished, compares source and target throughout the migration rather than once at the end, and maintains an audit trail so your team can identify every exception and demonstrate completion.
Cloud to cloud transfer
Move supported data directly between authorized cloud providers without routing every object through a user's workstation and the connection behind it.
Large data sets
Manage long running transfers and high object counts through a workflow designed for terabyte scale projects rather than desktop synchronization.
Recovery from interruption
Resume interrupted work from recorded progress instead of restarting the entire transfer and moving the same bytes twice.
Continuous verification
Compare source and target state during the migration and surface the mismatches that need attention while there is still time to act.
Exception handling
Separate failed or changed items for review, retry or documented disposition, so one bad object never hides inside a successful total.
Audit trail
Record transfer activity, verification results and exceptions in a form that technical staff and clients can both review.
Tell us the source provider, the target provider and the volume, and we will say whether DataTube fits the move before you plan the cutover.
Methodology
Four Steps From Mapping to a Verified Migration Record
-
Map
Confirm the source, the target, credentials, data scope, metadata requirements and provider limits before a single object moves.
-
Transfer
Move data in controlled work units while recording progress and provider responses as the migration runs.
-
Recover
Resume interrupted items and isolate exceptions without discarding the work that has already completed.
-
Verify
Reconcile source and target, document unresolved differences and produce the migration record you can hand to the client.
Want to see what a verified migration record looks like before the first object moves? Ask the product team to walk through an illustrative manifest.
Operating note
What Governs Speed and Fidelity
Achievable speed and metadata fidelity depend on provider APIs, rate limits, object characteristics, network conditions and the permissions available at both ends. We measure them on your providers during planning, so the schedule rests on real numbers instead of a best case.
Related Proprietary Software and Forensic Services
How to Define Acceptance Before the First Object Moves
Request the distribution, license terms, supported provider connections, installation requirements and support arrangements from the product team before you plan the migration, so the plan rests on what the current release does.
Define the source and the target precisely: the provider, the object or file types, the versions, the permissions, the account quotas and the metadata that must survive the move. Agree credentials with limited access, an expiry, a revocation path and a stated place where secrets are held.
Decide how a resume behaves. Define the checkpoints and how changed, overwritten, failed or deleted source objects are treated, so the second run is as predictable as the first.
Define acceptance in writing. Compare the agreed object counts, sizes, hashes where they are comparable, metadata and unresolved exceptions, and keep a dated manifest from both ends.
An illustrative manifest can show an object copied successfully while its access control metadata failed. That item remains an exception until it is corrected or explicitly accepted, because a completed byte transfer alone does not prove that metadata, versions and permissions match.
If acceptance criteria are still undefined, send the product team the object counts, metadata fields and exceptions that matter to you and we will write them into the plan.
Talk with an examiner
Tell Us What Has to Move and Match
Tell us the providers, the volume and the deadline. A GDF engineer will call or write back promptly to confirm the supported provider connections and how DataTube fits your migration or your matter.
Developed, supported and owned by GDF, a practice operating since 1992. Our 24/7 hotline is (800) 868-8189.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .