bhatti snapshot import
Import a snapshot archive written by bhatti snapshot export.
Synopsis
bhatti snapshot import <archive.tar.zst|-> [--name <snapshot-name>]
Description
Import registers a snapshot, not a running sandbox. - reads stdin; --name overrides the name stored in the archive. Resume separately with bhatti snapshot resume.
The destination must have the same architecture as the source (x86_64↔arm64 archives are not interchangeable) and the root base image identified by content. A memory snapshot additionally requires the same host OS and a CPU supporting every feature used by the saved guest: a Linux KVM memory checkpoint cannot resume on macOS HVF. A filesystem snapshot captures only the root disk; on the same architecture it can import across macOS↔Linux and cold-boot a fresh guest, without attached volumes or the source's network policy. Preserve volume data separately. If the matching base is missing, export again with --include-base. Memory snapshots carry RAM/CPU/device state, the root disk, attached-volume copies and network policy; restored volumes are cloned and re-attached. Server-side secret records and grant authorizations do not travel — configure those separately. Credentials already present in captured guest RAM or files remain included; treat archives as sensitive. This is a checkpoint transfer, not live migration.
Examples
# Copy an exported archive to a compatible host first
bhatti snapshot import dev-ready.tar.zst
bhatti snapshot resume dev-ready --name dev
# Register under another name
bhatti snapshot import dev-ready.tar.zst --name dev-ready-2
bhatti snapshot resume dev-ready-2 --name dev-2
# Stream without a local archive on the destination
ssh source-host 'bhatti snapshot export dev-ready --include-base' | bhatti snapshot import -
Options
| Flag | Default | Description |
| ---- | ------- | ----------- |
| --name <string> | exported snapshot name | Register under a different snapshot name. |
See Global flags for --url, --token, --json, --timing, --data-dir.
See also
bhatti snapshot export— create the archive- Move sandboxes between hosts — portability and step-by-step workflow