Save and recover work

Take a snapshot

Outcome You preserve the complete state of your Instance - files, tables, and Application configurations - as an immutable, time-stamped record.

Before you start

• You are in the Current state of your personal Instance.

• All work you want to preserve has been saved.

The procedure for creating a snapshot is the same regardless of the role taking it. See the canonical procedure: How-to › Common Workflows › Create a snapshot.

Take a snapshot before any major change to your work - before a risky refactor, before submitting an assignment, or at the end of a working session. The snapshot preserves the entire state, not just files, so you can roll back without losing your Application configuration.

Restore from a snapshot

Outcome You revert your Instance to a previous state captured in a snapshot.

Before you start

• You have taken at least one snapshot of the Instance.

• You understand that restoring will replace the Current state with the snapshot contents.

The procedure for restoring from a snapshot is the same regardless of the role doing it. See the canonical procedure: How-to › Common Workflows › Restore from a snapshot.

Restoring affects the entire Instance. Before any restore, Nuvolos automatically creates a snapshot of the current state so you can revert the restore if needed.

Delete a snapshot

Outcome You permanently remove a snapshot you no longer need, freeing up storage.

Before you start

• You have identified the snapshot you want to delete.

• You understand the action is irreversible.

The procedure for deleting a snapshot is the same regardless of the role doing it. See the canonical procedure: How-to › Common Workflows › Delete a snapshot.

If you delete files from your Current state but the data is still referenced in a snapshot, storage is not freed. To fully reclaim storage, delete the snapshots that contain the data as well. For the reasoning, see Concepts › Snapshots, distribution, and states.