Snapshot in. Open archive out.
Extract supported datafiles from a mounted, application-consistent snapshot or clone, away from production. Datafile recovery is Beta; supported output formats and source-specific limits still apply.
//What is verified here
- Reads supported mounted snapshot / clone datafiles BETA; storage provisioning is a separate step
- No connection to the live Oracle instance during extraction from the provided offline files
- 15 DBF export formats, including Parquet, Delta, Iceberg, Avro, ORC and Arrow; datafile recovery remains BETA
reclaimDB contains no vendor-specific SnapMirror / SRDF / EBS integration. It simply reads the .dbf of the provided replica — i.e. the snapshot is mounted with native storage tooling, then reclaimDB points at it. That is exactly what makes it vendor-neutral. "Scheduled export" = cron / Ansible, not a built-in scheduler.
The exported files can also supply analytics, data platforms and migration workflows. Datafiles made available from a standby environment are another source option within the supported file scope; their preparation and consistency must be established for that environment. The example below uses an application-consistent offline snapshot. See the FAQ for current requirements and the planned read-consistency extension.
//Step by step
Mount the snapshot / clone (off-host)
reclaimDB runs against the files of the storage replica — never the live DB. How the snapshot is provisioned (NetApp SnapMirror, Dell SRDF, ZFS, AWS EBS …) is the storage's job; reclaimDB then reads the mounted .dbf.
# Example: a ZFS clone or a mounted snapshot
mount /dev/.../snap_2026-06-19 /mnt/snap
ls /mnt/snap/oradata/*.dbfExtract the snapshot on a separate host
reclaimdb autoscan /mnt/snap/oradata reclaimdb restore -m meta.json --parquet /archive/2026-06-19/ /mnt/snap/oradata/*.dbf
The extraction reads the supplied snapshot files. Shared storage resources can still affect the production environment.
Write to future-proof open formats
# Data-lake formats for long retention: reclaimdb restore -m meta.json --delta /archive/delta/ /mnt/snap/oradata/*.dbf reclaimdb restore -m meta.json --iceberg /archive/iceberg/ /mnt/snap/oradata/*.dbf
Scheduled via cron — a license- & version-independent archive
Scheduling is an ops pattern (cron / Ansible / CI), not a built-in daemon:
# /etc/cron.d/reclaimdb-archive — daily at 02:00 0 2 * * * oracle reclaimdb --quiet restore -m /etc/meta.json \ --parquet /archive/$(date +\%F)/ /mnt/snap/oradata/*.dbf
//Relevant exit codes
Test this case on your data
Send us the kind of source you actually have — a .dmp, a .dbf, an RMAN backup piece or a storage snapshot. You get a signed evaluation binary, a sample report, and an honest assessment of which paths apply to your case.