fly vol ↔ alias:[volume|volumes] to manage volume mounts for fly app, to persist local storage on Fly Machine; NVMe slice

aka Fly-Volume, Fly-Volumes

default --require-unique-zone=true to ensure Fly Volumes in same region distribute among different Hardware Server

Fly Volumes are INDEPENDENT of each other & NOT DUPLICATED automatically

Fly Volumes can extend in -s size but not shrink - only integer GB values allowed - which effectively limits # app volumes to 3 MAX

?does Fly Snapshots count towards 3GB free limit?

default daily snapshot store for 5d

fly.io DOES NOT automatically replace Fly Volumes on drive failure!

snaps

to list snapshots for __vol_ID, backstop for downtime NOT backup - backups on separate offsite loc

fly vol snaps list __VOL_ID

References