Skip to content

Add tip for creating a Machine with a volume from a snapshot #2381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kcmartin merged 1 commit into from
Apr 16, 2026
Merged

Add tip for creating a Machine with a volume from a snapshot #2381

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions volumes/snapshots.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,18 @@ Restore the data from a volume by creating a new volume from a snapshot:

For options, refer to the [`fly volumes create` docs](/docs/flyctl/volumes-create/) or run `fly volumes create --help`.

## Create a Machine with a volume from a snapshot

Create the volume and the Machine in one command:

```cmd
fly scale count --with-new-volumes --from-snapshot <snapshot id> 1
```

`--with-new-volumes` creates a new volume instead of reusing an existing one. `--from-snapshot` populates that volume from the snapshot. The trailing `1` is the Machine count.

For options, refer to the [`fly scale count` docs](/docs/flyctl/scale-count/) or run `fly scale count --help`.

## List snapshots and their stored sizes

Snapshots for each volume are stored incrementally, so only data that has changed since the previously stored snapshot consumes additional storage. The total stored size of the snapshots is used for [Volume Snapshot billing](/docs/about/billing/#volume-snapshot-billing).
Expand Down
Loading