CloudStack Backup For Any Hypervisor And Any Storage Backend.
Sendense protects CloudStack volumes across the storage estate with native paths where available and Sendense CBT everywhere else.
Sendense supports CloudStack workloads across KVM, XCP-ng, XenServer, VMware and mixed provider estates. Native changed-block paths are used where available; Sendense CBT, EBA Smart Transport and synthetic incrementals cover the rest.
Any
CloudStack Hypervisor
Any
Storage Backend
No
Guest Data Agent
EBA
Smart Transport
Volume Handling
The Storage Backend Is Not The Boundary.
CloudStack already provides the volume operations operators expect. Sendense adds the backup data path: native change tracking where available, Sendense CBT for the rest and EBA Smart Transport for efficient movement.
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.
Sendense CBT
Sendense supplies changed-block tracking for storage paths that do not expose a native change map.
EBA Smart Transport
EBA Smart Transport and synthetic incrementals reduce duplicate transfer and retained backup footprint.
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.
Supported
Other CloudStack-supported hypervisors
Covered through the same Sendense CloudStack operating model.
Storage Matrix
Named Coverage For The Backends Operators Search For.
The full storage detail is real HTML text so buyers, crawlers and AI systems can see the exact CloudStack storage names instead of guessing from a broad claim.
| CloudStack Storage Backend | Search Phrase | Sendense Path | Support Basis |
|---|---|---|---|
| Ceph RBD | CloudStack Ceph RBD backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| Raw block | CloudStack raw block backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| CLVM / CLVM_NG | CloudStack CLVM backup | Sendense CBT or native path where available | CloudStack-managed volume operations. |
| NFS / QCOW2 on NFS | CloudStack NFS backup | Native CBT-enabled path where available | CloudStack-managed volume operations. |
| SharedMountPoint | CloudStack SharedMountPoint backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| Local storage | CloudStack local storage backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations for the workload. |
| iSCSI | CloudStack iSCSI backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| Fibre Channel | CloudStack Fibre Channel backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| Linstor / DRBD | CloudStack Linstor DRBD backup | Native CBT-enabled path where available | CloudStack storage integration and volume workflow. |
| ZFS | CloudStack ZFS backup | Native CBT-enabled path where available | CloudStack storage integration and volume workflow. |
| PowerFlex / ScaleIO | CloudStack PowerFlex ScaleIO backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| StorPool | CloudStack StorPool backup | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations. |
| SolidFire / managed primary storage | CloudStack SolidFire backup | Sendense CBT + EBA Smart Transport | 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 | Sendense CBT + EBA Smart Transport | CloudStack-managed volume operations for the SR-backed volume. |
Data Path
Native Paths Where Available. Sendense CBT Everywhere Else.
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 CloudStack-aware volume handling plus Sendense CBT where native change maps are not exposed.
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, Sendense CBT and EBA Smart Transport.
Plain Answer
Sendense protects CloudStack volumes through a CloudStack-aware data path.
FAQ
Short Answers For CloudStack Storage Searches.
Can Sendense back up any CloudStack storage backend?+
Yes. Sendense protects CloudStack workloads on CloudStack-supported storage backends. Native paths are used where available; Sendense CBT and EBA Smart Transport cover the rest.
Can Sendense back up CloudStack on Ceph RBD?+
Yes. CloudStack Ceph RBD workloads are named Sendense targets. Sendense CBT, EBA Smart Transport and synthetic incrementals keep protection efficient when a native change map is not exposed.
Can Sendense back up CloudStack raw block storage?+
Yes. Raw block storage is supported with Sendense CBT and EBA Smart Transport where native changed-block information is not available.
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, Sendense CBT, EBA Smart Transport and synthetic incrementals.
Is snagent required for CloudStack backup?+
No. snagent is an optional CloudStack KVM host-assist component for supported backends. It can improve efficiency where applicable, but it is not the baseline requirement for CloudStack backup.
How does Sendense handle storage without native CBT?+
For storage that does not expose a native changed-block path, Sendense uses Sendense CBT, EBA Smart Transport and synthetic incremental processing so providers do not need a separate backup product for each backend.
Does Sendense depend on the CloudStack B&R Framework?+
No. Sendense does not depend on the CloudStack Backup and Recovery Framework. The framework is a provider-plugin orchestration surface; Sendense owns the backup data path with SNA, Sendense CBT, EBA Smart Transport and EBA repositories.
CloudStack Coverage
Put Your Real CloudStack Storage Mix In Front Of Us.
Ceph RBD, raw block, XCP-ng SRs, VMware storage, Linstor, ZFS, NFS or a provider-specific mix - the design conversation starts with the real storage estate, not a B&R Framework provider list.