What Is Sendense

Overview

An overview of Sendense as a backup, recovery, and disaster-recovery platform.

ReadyCurrentoverviewplatformstart-here

Overview

Sendense protects virtual machine workloads, keeps recoverable history in EBA, and gives administrators recovery paths across supported platforms.

The platform vocabulary starts with SHA for orchestration, SNA for backup proxy work, EBA for backup storage and recovery points, SCA for provider-scale management, Sendense Controllers for replication targets, and snagent for supported CloudStack KVM hypervisor hosts.

What Sendense Does

Backs up protected workloads into governed EBA repositories.
Supports recovery operations such as full VM restore, file and item recovery, and DR failover where configured.
Coordinates appliance lifecycle, protection patterns, replication patterns, indexing, RBAC, reporting, and system health through SHA.
Lets service providers manage MSP or CSP deployment shapes through SCA when that operating model is used.

Components At A Glance

SHA

Sendense Hub Appliance. The orchestration hub for protection patterns, replication patterns, recovery operations, EBA repositories, RBAC, health, reports, and appliance lifecycle.

SNA

Sendense Node Appliance. A virtual appliance that acts as a backup proxy and runs the EBA Smart Transport role.

EBA

Enterprise Block Archive. The Sendense backup storage and recovery-point system for protected workload data.

EBA-ST

EBA Smart Transport. The SNA-side smart transport role for backup proxy data movement.

SCA

Sendense Central Appliance. The provider-side appliance for MSP telemetry and controlled remote operations, and for CSP billing, API, provisioning, and license management.

Sendense Controllers

Per-VM destination appliances used by controller-backed replication patterns and failover workflows.

snagent

The CloudStack KVM hypervisor host agent used for host-assisted changed-block tracking on supported storage backends.

Operating Models

Sendense supports three top-level operating models: a standalone customer SHA, MSP-managed customer SHAs with SCA above them for telemetry and delegated remote operations, and CSP-provisioned tenant SHAs managed through provider automation.

SHA remains the hub for each customer or tenant environment in all three models.

Where To Start

Start with the component model and architecture overview to learn the platform vocabulary and how the pieces connect.

Then move into deployment planning and infrastructure requirements when preparing an environment, or into the backup, recovery, and DR areas when designing protection and recovery workflows.