Sendense Does Not Depend On The CloudStack B&R Framework.
That is intentional. The CloudStack B&R Framework is a provider-plugin orchestration surface, not a universal changed-block backup data path.
Sendense protects CloudStack with its own protection plane: SNA backup proxies, CloudStack-aware capture, EBA Smart Transport, EBA repositories and CloudStack-aware recovery workflows for mixed storage estates.
Architecture Choice
The Framework Is Not The Backup Engine.
CloudStack's framework can expose backup actions for selected plugins. Sendense puts correctness, source-path selection, transfer efficiency and repository behavior in the Sendense data path instead.
The B&R Framework Is An Orchestration Layer
CloudStack's Backup and Recovery Framework abstracts backup provider operations into CloudStack UI and API actions. It does not give every storage backend a universal changed-block data path.
Sendense Owns The Protection Data Path
Sendense uses SNA, qualified native paths, CloudStack-aware full-source reads and EBA repositories so source-path correctness, transfer efficiency and retention are not limited by a CloudStack provider plugin.
Storage Coverage Comes First
Ceph RBD, raw block, XCP-ng storage repositories, iSCSI, Fibre Channel, StorPool, PowerFlex and other CloudStack storage paths stay in one Sendense operating model.
Direct Comparison
CloudStack Plugin Surface vs Sendense Protection Plane.
Apache documents the B&R Framework as a plugin model for third-party backup providers. That is a different problem from universal storage-aware changed-block protection.
| Topic | CloudStack B&R Framework | Sendense |
|---|---|---|
| Primary purpose | Expose provider-specific backup actions through CloudStack backup offerings, schedules and restore APIs. | Protect CloudStack workloads through an independent backup plane with SNA, CloudStack-aware capture, EBA Smart Transport and EBA. |
| Changed-block tracking | No universal CBT layer across every CloudStack storage backend. | Uses qualified native paths where available and safe CloudStack-aware full-source reads elsewhere. |
| Storage model | Depends on the selected provider plugin and its tested storage paths. | Designed for mixed provider estates: Ceph RBD, raw block, NFS/QCOW2, ZFS, Linstor/DRBD, XCP-ng SRs, VMware storage and more. |
| Repository economics | Repository behavior depends on the chosen plugin and backup target. | EBA provides deduplication, compression, retention controls and efficient restore behavior as part of the Sendense platform. |
| Tenant surface | CloudStack UI/API backup actions where the chosen plugin supports them. | Provider-defined service surface through Sendense, SCA/API models, reports, evidence and managed BaaS or DRaaS workflows. |
Sendense Data Path
Built For The CloudStack Estate You Actually Run.
Sendense treats CloudStack as the source platform, but the backup data path is Sendense-owned. That is what lets one protection model cover storage types that do not share the same native change-tracking primitive.
Discover CloudStack
Sendense maps zones, hosts, tenants, volumes, storage paths and VM placement through scoped CloudStack credentials.
Use The Right Data Path
Qualified native or host-assisted changed-block paths are used where supported. Other supported storage uses CloudStack-aware full-source reads and EBA repository deduplication.
Store In EBA
Protected blocks land in governed EBA repositories with deduplication, compression, retention and restore controls.
Recover And Prove
Operators restore, validate, migrate or build DRaaS services from the same recovery-point model.
FAQ
Short Answers For Framework Questions.
Does Sendense require the CloudStack B&R Framework?+
No. Sendense does not depend on the CloudStack Backup and Recovery Framework. Sendense protects CloudStack workloads through its own CloudStack-aware protection plane, using SNA, CloudStack-aware capture, EBA Smart Transport and EBA repositories.
Why not just use the CloudStack B&R Framework?+
The framework is a provider-plugin orchestration surface. It can expose useful CloudStack UI and API actions, but it is not a universal changed-block data path across all CloudStack storage backends. Sendense is built for mixed storage estates where backup correctness, source-path selection and repository efficiency need to live in the protection platform.
Can Sendense still protect CloudStack storage that is not covered by a B&R plugin?+
Yes. Sendense covers CloudStack-supported storage paths through native or host-assisted changed-block paths where available, and through CloudStack-aware full-source reads plus EBA Smart Transport where qualified native or host-assisted change maps are not exposed.
Does Sendense give tenants CloudStack self-service backup buttons?+
Sendense is not positioned as a CloudStack B&R Framework plugin that adds backup buttons to the standard CloudStack instance screen. It is a provider-controlled backup and recovery platform for managed BaaS, DRaaS, reporting, evidence, retention and recovery workflows.
CloudStack Backup
Evaluate The Protection Plane, Not The Plugin Checkbox.
Bring the storage mix: Ceph RBD, raw block, XCP-ng SRs, VMware storage, Linstor, ZFS, NFS, iSCSI, Fibre Channel or provider-specific arrays.