Proprietary API /v2/volumes/{volume_id}/snapshots instead of OpenStack /v3/{project_id}/snapshots.
Explicitly crash-consistent only, no automatic filesystem consistency (requires manual power-off/sync); OpenStack snapshots can use quiescing drivers for apps like databases.
Snapshots billed separately based on block-level used size (may exceed filesystem due to trim); OpenStack typically similar. See the DigitalOcean pricing page for current rates.
Can create new volumes only in same region as snapshot; OpenStack snapshots more flexible for cross-region with upload/download.
Crash-consistent point-in-time copies stored incrementally in Cloud Storage (geo-redundant by default), unlike Cinder snapshots which depend on backend (often full copies).
Two types: Standard (faster recovery) and Archive (cheaper long-term); supports snapshot schedules (standard only).
Global by default, shareable across projects/regions/zones with network egress costs for cross-region restore; regional scoping (preview) for location control.
Frequency limit: max 6 snapshots per disk every 60 minutes.
No support for volume snapshots in API or console; explicitly stated 'we do not provide Backups or Snapshots for Volumes' and server snapshots exclude volumes.
Workarounds like rsync/dd to new volume required, unlike Cinder's create/delete/get/manage_snapshot API.
Recent confirmations (2026) show no addition of feature.
Created as Image type='snapshot' via server action; stored under /images.