Skip to main content

​
Overview

On‑prem environments use a streamlined version of Resource Management focused on storage capacity measured in terabytes (TB). Tokens are not applicable to on‑prem devices. The goal is to keep your system responsive by capping how many writable (Active) projects you keep on the device and automatically freeing space when you exceed your budgets. If your organization is on the Pro or Enterprise plan, you’ll see usage in the UI. Legacy plans do not show these controls.

​
Key concepts

Active storage (TB): Active projects are 3D Projects with a full CT scan and Reconstruction wherein new analyses and data can be authored. When a scan completes, the resulting project is Active and supports creating new data via Recipes and Voyager tools. Read‑Only projects: A Read‑Only project is a 3D Project wherein new analyses and data can no longer be authored. The full set of resulting Analyses, Data Objects, Meshes, Bookmarks, etc. remain available for inspection and sharing, but new analyses cannot be created.
  • On on‑prem devices, moving a project to Read‑Only is destructive to reclaim space: reconstruction and radiographs are deleted.
Pinned projects: Active projects that are explicitly kept in the Active tier. Pinned projects remain Active and cannot be made Read‑Only automatically while pinned. Use pins judiciously to protect critical work.
  • Most on‑prem systems ship with roughly 75% of usable space for Active project data so your team can comfortably work on current projects while leaving room for system overhead and read‑only records.

​
How project migration works (on‑prem)

When your organization is on Pro or Enterprise:
  1. When Active TB is exceeded and Automatic Read‑Only Migration is enabled, least‑recently‑accessed projects are migrated to Read‑Only to free space.
Notes:
  • On on‑prem devices, Read‑Only migration deletes reconstruction and radiographs to reclaim space. The project remains viewable in Voyager, but cannot be returned to a writable state unless you rescan or restore from your own backups.
  • If you turn off the Read‑Only migration toggle, projects will remain Active even if you exceed Active TB. This prevents deletion but risks running out of local disk space; discuss options with your Lumafield team if you need more capacity.

​
Manager view

  • The top bar shows Active usage to all members; Manager dashboard shows detailed limits and migration settings.
  • It is critical to keep Auto‑Archive enabled to maintain headroom on the device as usage grows.

​
Example scenario

Your device has:
  • Active TB: 50 TB
  • Automatic Read‑Only Migration: Enabled
If you exceed 50 TB of Active projects, Voyager will migrate projects individusally by (least‑recently‑accessed) from Active to Read‑Only. On on‑prem devices this frees space by deleting reconstruction and radiographs for those projects.

​
Glossary

  • Active (TB): Writable project tier on device.
  • Read‑Only (on‑prem): View‑only state that reclaims space by deleting reconstruction and radiographs.
  • Least‑recently‑accessed: Order Voyager uses to pick projects for migration when limits are exceeded.

​
FAQ

  • Can a Read‑Only project be restored to writable on on‑prem?
    • Not automatically. Since reconstruction and radiographs are deleted to free space, you’d need to rescan or restore from your own backup.
  • What happens if I disable Automatic Read‑Only Migration?
    • Projects won’t move to Read‑Only automatically, even if Active TB is exceeded. This prevents deletion but risks running out of disk space. Talk to Lumafield about capacity options.