GitHub user DRDAVIDBANNER edited a comment on the discussion: What does Snapshots, Backups, and Incremental Snapshots mean in CloudStack
>From an operator/MSP perspective, we treat snapshots and backups as separate >things even where the underlying CloudStack terminology overlaps. We generally think of a snapshot as a platform-level point-in-time mechanism, whereas a backup service needs to cover the wider operational requirements: independent retention, policy management, recovery workflows, monitoring, reporting and ideally recovery into another location for DR. At Quadris, we use Sendense for backup and DRaaS across our CloudStack environment rather than relying solely on CloudStack snapshots. One of our requirements was support for block-storage environments as well as CloudStack-aware recovery. Full disclosure: I am involved with [Sendense](https://sendense.com/cloudstack-backup), but we have also been running it operationally in the Quadris cloud for around six months. From our perspective, the important question is less about whether CloudStack calls an object a “snapshot” or “backup,” and more about whether the overall design meets the required RPO, RTO, retention and failure-domain requirements. GitHub link: https://github.com/apache/cloudstack/discussions/12475#discussioncomment-17663212 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
