Illustration of a mapping project on a laptop with external SSD drives and a protected storage case

DJI Terra Project Backup & Archiving Guide

PROJECT RECOVERY & LONG-TERM REPRODUCIBILITY

Keep enough information to recover the work, not just the final map

A useful DJI Terra project backup preserves the observations, project dependencies and decisions behind the accepted result. Keeping one exported model is a delivery copy; recovering or reviewing the reconstruction can require substantially more information.

Design the archive around two questions: can the team recover the files after a failure, and can a future operator understand how the accepted revision was produced?

Decide what the archive must preserve

Inventory the actual project rather than relying on a single folder name. Use Terra’s project result-folder access to identify the produced files, then map their dependencies and source locations for the installed release.

A practical project archive
Group What to retain Why it matters
Original observations Original images or recording folders and associated positioning files. Allows the source to be reviewed or processed again.
Project and dependencies Native project files and the inputs they reference. Supports reopening the intended project.
Processing record Software release, relevant settings and input selection. Explains how a revision was created.
Validation evidence Reports, independent checks and review notes. Connects acceptance to the delivered result.
Accepted exports The complete approved delivery package. Preserves what the recipient actually received.
Revision manifest Dates, owner, status and file inventory. Distinguishes draft, accepted and superseded work.

Preserve the source folder relationships, especially when a recording includes several associated files. A native project file may depend on external data; its presence alone does not prove that the archive is complete.

Separate source, working revisions and accepted deliveries

Use an explicit naming convention. One example is SiteA_2026-10-14_R01, with a manifest stating whether R01 is a draft or accepted delivery. The name is an organizational example, not a Terra-required format.

  • Keep an unchanged source copy separate from experiments.
  • Identify the input selection and settings used by each accepted revision.
  • Record repairs or transformations applied after reconstruction.
  • Retain the recipient’s delivery package as its own identified revision.
  • Document which files are disposable working data and which remain necessary.

Avoid a chain of folders named “final”, “final-new” and “final-latest” with no ownership or acceptance record. Revisions should explain the change: different image selection, corrected reference information, a new export or a presentation-only edit.

Create copies that survive different failure modes

A second folder on the same drive does not protect against the loss of that drive. Plan separate backup storage and a copy protected from changes to the active workstation. CISA recommends offline backups and regular recovery testing in its ransomware guidance.

Agree the copy schedule with the project owner. Protect significant milestones: source ingestion, accepted processing and final handover. Use a completed, consistent project state for an archive, or a backup method validated by the organization for active files.

Distinguish synchronization from recovery

A synchronized location can reproduce a mistaken deletion or overwrite. Confirm whether the chosen service provides a recoverable history and whether the team has actually tested its restoration process.

Record file counts and sizes. Where appropriate, retain checksums so later copies can be compared with the archived inventory. These checks complement a restoration test; they do not replace it.

Test restoration before removing working data

  1. Select one completed representative project and a separate restore location.
  2. Restore the archived files without changing the retained archive.
  3. Confirm the expected source files and associated dependencies are present.
  4. Open the project using an authorized, compatible software setup and resolve its input paths.
  5. Open the accepted exports in the intended receiving application.
  6. Compare the restored files and key review observations with the manifest.
  7. Record the result, missing dependencies and corrective actions.

A data restore does not transfer a software entitlement or bypass account and device binding. Plan the recovery workstation’s authorization separately. Reprocessing in a different software release may produce differences, so preserve the original accepted exports and release record.

Our quality-report guide helps identify review records worth retaining. Agree retention periods and deletion decisions with the responsible project owner rather than selecting them arbitrarily.

DJI Terra project backup FAQ

Is an exported OBJ or GeoTIFF a complete project backup?

It preserves a particular output. Reopening or reconstructing the project may also require native files, original observations and other dependencies.

Can I delete all temporary files after processing?

First identify their role in the installed release and test the archive. Delete working data only after confirming it is not needed for the agreed recovery objective.

Will opening an archive guarantee identical reprocessing?

The original accepted files can be preserved and checked. Reprocessing also depends on software, settings, inputs and the computing environment; document those conditions.

Plan the project lifecycle before processing at scale

Tell Drone Emotions the reconstruction workflow, expected dataset size and deployment needs. We can help review the Terra software setup while your team defines its archive and recovery requirements.

Official documentation

Independent guide by Drone Emotions. Documentation reviewed on 14 October 2026. Consult the documentation for the installed software and capture-system releases.