Your org's volume snapshots (paged)

List your org's snapshots with their source node, state, size, image and any expiry. A ready snapshot preserves the captured disk after its source machine stops or fails. triggered_by tells who took each snapshot. It is customer for a snapshot your org took, and system for one the platform took to keep a copy of a parked disk. A system snapshot does not bill storage. Failed uploads remain visible, and the platform retries while the source disk stays parked. Snapshots expire only when you set an expiry. A snapshot's region identifies its storage location; downloads across regions can take longer. A snapshot that shows a region is stored on one storage cluster in one datacenter. A snapshot without a region is in central storage, which keeps copies in several availability zones. Direct restores require a compatible node type and image.