Vultr Snapshots / Auto Backups

Quake AI concept: Snapshots

• Vultr exposes this as two separate features, "Snapshots" and "Auto Backups", rather than one Nova instance-snapshot object model. The snapshots page describes "instance snapshots" as full-state copies for cloning, disaster recovery, and replication, while the backups page describes automated scheduled snapshots with retention policies (Vultr Snapshots Setup and Management, Vultr Backups Setup and Management).
• The Vultr docs present snapshots as point-in-time copies of compute instances, and they are managed as Vultr resources that can be restored or deleted from the account. OpenStack Nova snapshots are usually modeled as images or server backups through API resources rather than a separately branded snapshot/backups feature with its own console actions (Vultr Features, Vultr Snapshots Setup and Management).
• Vultr’s documentation does not state any requirement that the instance be shut off before taking a snapshot, and it does not document Nova-style snapshot create-time parameters in the page content. The canonically documented workflow is simply to create or restore the snapshot from the Vultr console, with no API endpoint called out on the snapshots page (Vultr Snapshots Setup and Management).
• Vultr auto backups are described as automatically created and stored regular backups with flexible retention policies, and the docs note that deleting backups can free storage space. That is operationally different from OpenStack Nova, where backup/snapshot behavior is not presented as a separately billed managed retention service in the canonical docs for this resource (Vultr Backups Setup and Management).