/
How Do I Create a Server Snapshot?

How Do I Create a Server Snapshot?

A server snapshot is a point-in-time backup of a virtual machine’s disk. In Spinup, snapshots are per-disk and are used to preserve or recover the state of your data and system configuration.

Snapshots are especially useful before making major changes, applying patches, or modifying installed software. If something goes wrong, you can restore the disk back to its snapshot state.

Automatic vs. Manual Snapshots

Snapshot Type

Frequency

Retention

Use Case

Snapshot Type

Frequency

Retention

Use Case

Automatic (CPM)

Nightly

14 days

Disaster recovery, minimal setup

Manual

User-initiated

Until deleted

Pre-change backups, long-term saves

Nightly automated snapshots are labeled as CPM and cannot be renamed. Manual snapshots can be named and retained indefinitely.

Key Behavior

  • Snapshots are per-disk: If your server has multiple attached disks, you must snapshot each one individually.

  • Creating a snapshot does not stop the server, though consistency is best when the server is powered off or the disk is quiesced.

  • Snapshots can be restored at any time to revert the disk to a previous state.

  • Snapshots do not include RAM or CPU state, only persistent disk data.

How to Create a Snapshot

  1. Navigate to the Server
    From your Spinup dashboard, go to the server you want to back up.

  2. Identify the Disk to Snapshot
    Spinup supports snapshotting each disk individually. Determine which disk holds the data or configuration you want to preserve.

  3. Click the Snapshot Icon
    On the server details page, click the camera icon next to the disk you want to snapshot.

  4. Enter a Description
    Add a meaningful description to help you identify the snapshot later (e.g., Before major app upgrade).

    • The creation date is stored automatically.

    • Empty descriptions are not allowed.

  5. Click “Create”
    Your snapshot will appear within seconds. You can monitor progress via the Latest Tasks panel.

Best Practices

  • Snapshot before risky changes such as OS upgrades, software reconfiguration, or large file imports.

  • Label clearly: Use descriptive names so future-you knows what the snapshot contains.

  • Coordinate with server activity: For application servers or databases, consider stopping services before snapshotting to avoid partial writes.

Need Help?

Snapshots are a simple but powerful tool to help you manage risk and keep your Spinup servers recoverable