Backup model

MoveStack’s backup and recovery model

How MoveStack treats full backups, snapshots, archive export, and restore as one coherent model for Node.js and Next.js apps.

MoveStack does not treat backup as just another file. The core idea is that a backup only matters if it stays tied to a believable recovery path.

What that means in practice
  • A full backup is a restorable snapshot, not just an artifact
  • Snapshot, archive export, and restore belong to one model
  • Backup and recovery should not drift into unrelated workflows
  • Backup value is measured by recoverability
The MoveStack model

MoveStack treats the full-backup snapshot as the primary recovery unit. That same unit can later be deployed into a target, exported as an archive, or restored in a controlled way. This keeps backup and recovery close to each other instead of splitting them apart.

Why this matters

Many teams create backups with one tool and improvise recovery with another. That leaves a gap exactly where operational confidence should be strongest.

Core facts

Full backup requires a license
Snapshot list and preview path are free
Archive export/import stays inside the same recovery model
Verified restore belongs to the licensed path

FAQ

Is a snapshot the same thing as a backup?

Not always. A snapshot is the general recovery unit. A full backup is the licensed, true backup mode of that unit.

Why is restore part of the backup model?

Because backup value is defined by whether it can restore a working target in a controlled way.

Related pages

DownloadHelpGuides
MoveStack’s backup and recovery model | MoveStack