Snapshots

Quake AI concept: Snapshots

• Vultr’s snapshots are documented as instance snapshots that capture the full state of compute instances, rather than a separate OpenStack Cinder-style volume snapshot object. The snapshots page describes them as a way to clone, restore, or replicate an instance state, which is broader than a block-volume-only resource. (Vultr Snapshots Setup and Management)
• The docs say snapshots preserve instance configurations but do not retain the original IP address when deployed. That differs from OpenStack patterns where a server or volume snapshot is not itself defined as losing or changing an IP identity because IP assignment is handled separately by Neutron. (Vultr Compute, Vultr Snapshots Setup and Management)
• Vultr’s compute docs state that restoring from a backup permanently overwrites disk data and cannot be undone, so restore is destructive. OpenStack Cinder snapshots are typically used as a source for creating new volumes or restoring data, but the Vultr docs explicitly frame restore as an irreversible overwrite action. (Vultr Compute)
• The Vultr compute docs also state that compute instances cannot be downsized to smaller plans due to data loss risk, and that downsizing from snapshots is not possible because of non-sequential disk storage. That operational constraint is not how OpenStack volume snapshots work, where a snapshot is detached from instance flavor sizing and can be used to create a new volume of selectable size. (Vultr Compute)