CloudStack Storage And Hypervisor Compatibility Matrix.
Check the Sendense data path, host-assist needs and deployment basis for the CloudStack estate you operate.
Compare named hypervisors and storage backends in one planning reference. Each row identifies how Sendense protects the workload and what must be available before commissioning.
Named
Backend Coverage
Path
Protection Method
Assist
Host Requirements
Plan
Deployment Basis
Volume Handling
Plan The Data Path Before Commissioning.
Start with the actual hypervisor and storage backend, then record the selected Sendense protection path, required CloudStack operations, optional host assist and network prerequisites.
CloudStack Volume State
Sendense coordinates with CloudStack volume state so protected data is captured at the infrastructure layer.
Protected Working Copy
The Sendense workflow uses CloudStack-managed volume handling for backup, restore and recovery operations.
Source-Aware Capture
Storage paths without a qualified native or host-assisted change map use a CloudStack-aware full-source scan and read.
EBA Smart Transport
EBA Smart Transport and repository deduplication reduce duplicate retained data; they do not avoid a required full source read.
Hypervisor Coverage
Built Around CloudStack, Not One Hypervisor.
KVM, XCP-ng, XenServer and VMware estates can all use the same Sendense operating model without making one hypervisor the boundary of support.
Supported
KVM
CloudStack-aware volume handling, with native or host-assisted optimisations where available.
Supported
XCP-ng / XenServer
Supported through the same Sendense CloudStack operating model.
Supported
VMware vSphere
Supported through CloudStack and VMware storage workflows.
Storage Matrix
Compare Backends, Data Paths And Requirements.
Use this matrix during discovery and design reviews to turn a storage inventory into a documented Sendense deployment plan.
| CloudStack Storage Backend | Protection Scenario | Sendense Path | Support Basis |
|---|---|---|---|
| Ceph RBD | CloudStack Ceph RBD backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| Raw block | CloudStack raw block backup | Full-source read + EBA; eligible patterns on version-aware repositories can use Sendense CBT for synthetic-incremental storage; first and forced fulls stay genuine | CloudStack-managed volume operations. |
| CLVM / CLVM_NG | CloudStack CLVM backup | Qualified native path or full-source read | CloudStack-managed volume operations. |
| NFS / QCOW2 on NFS | CloudStack NFS backup | Qualified snagent host-assisted changed-block path | CloudStack-managed volume operations. |
| SharedMountPoint | CloudStack SharedMountPoint backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| Local storage | CloudStack local storage backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations for the workload. |
| iSCSI | CloudStack iSCSI backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| Fibre Channel | CloudStack Fibre Channel backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| Linstor / DRBD | CloudStack Linstor DRBD backup | Qualified snagent host-assisted changed-block path | CloudStack storage integration and volume workflow. |
| ZFS | CloudStack ZFS backup | Qualified snagent host-assisted changed-block path | CloudStack storage integration and volume workflow. |
| PowerFlex / ScaleIO | CloudStack PowerFlex ScaleIO backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| StorPool | CloudStack StorPool backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| SolidFire / managed primary storage | CloudStack SolidFire backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations. |
| VMFS / vSAN / vVols | CloudStack VMware storage backup | CloudStack and VMware storage workflow | CloudStack and VMware volume operations for VM disks. |
| DatastoreCluster | CloudStack DatastoreCluster backup | CloudStack and VMware storage workflow | CloudStack and VMware volume operations for VM disks. |
| XCP-ng storage repositories | CloudStack XCP-ng backup | CloudStack-aware full-source read + EBA | CloudStack-managed volume operations for the SR-backed volume. |
Data Path
Qualified Native Paths Where Available. Safe Full-Source Reads Elsewhere.
Storage-specific acceleration is useful, but the CloudStack protection model does not depend on every backend exposing the same CBT primitive.
Built Around CloudStack-Aware Volume Handling
Sendense does not need every storage array to expose the same changed-block API. The protection workflow uses qualified native or host-assisted change tracking where available and CloudStack-aware full-source reads elsewhere.
Optimised Paths Stay Optimised
Where a native, storage-level or host-assisted changed-block route exists, Sendense uses it. Those paths make protection faster, but they are not the limit of support.
No Workload Data Mover
Backup data does not need to move through software inside the protected VM. The protected data path stays aligned to CloudStack-aware volume operations and EBA Smart Transport.
Plain Answer
Sendense protects CloudStack volumes through a CloudStack-aware data path.
FAQ
Planning Answers For CloudStack Storage.
Can Sendense back up any CloudStack storage backend?+
Yes. Sendense protects CloudStack workloads on CloudStack-supported storage backends. Qualified native paths are used where available; other supported paths use CloudStack-aware full-source reads and EBA repository deduplication.
Can Sendense back up CloudStack on Ceph RBD?+
Yes. CloudStack Ceph RBD workloads are named Sendense targets. Without a qualified native or host-assisted change map, Sendense scans and reads the full source while EBA deduplicates retained repository data.
Can Sendense back up CloudStack raw block storage?+
Yes. Raw block storage is supported through a CloudStack-aware full-source read with EBA repository deduplication. Eligible RAW Block protection patterns on version-aware EBA repositories can use Sendense CBT: the source is still fully scanned and read, the first and explicitly forced fulls remain genuine fulls, and suitable later recovery points can be represented as synthetic incrementals when eligibility and integrity checks pass.
Does Sendense support XCP-ng or XenServer in CloudStack?+
Yes. Sendense support is based on the CloudStack workload and storage model. XCP-ng and XenServer workloads are covered through one Sendense operating model.
Does Sendense move backup data through the VM?+
No. Sendense does not require backup data to move through software inside the protected VM. Protection uses CloudStack-aware volume operations and EBA Smart Transport. Without qualified native or host-assisted change tracking, the source is scanned and read in full.
Is snagent required for CloudStack backup?+
Not for every CloudStack path. RAW Block does not use snagent, but the qualified QCOW NFS, ZFS, and LINSTOR DRBD host-assisted modes require a healthy, correctly placed snagent and can fail if it is unavailable.
How does Sendense handle storage without native CBT?+
For supported storage without a qualified native or host-assisted changed-block path, Sendense scans and reads the full source and uses EBA repository deduplication. Eligible RAW Block protection patterns on version-aware EBA repositories can use Sendense CBT while retaining that full source scan and read. The first and explicitly forced fulls remain genuine fulls; suitable later recovery points can be represented as synthetic incrementals when eligibility and integrity checks pass.
How should I use the CloudStack compatibility matrix?+
Use it to identify the hypervisor and storage backend, confirm the selected Sendense data path, and capture any CloudStack, host-assist or network prerequisites in the deployment plan before commissioning.
Compatibility Review
Turn The Matrix Into A Deployment Plan.
Bring the real hypervisor and storage inventory. Sendense will confirm the protection path, prerequisites and commissioning plan for each part of the estate.