EBA
Immutable, high-efficiency backup storage. Built into Sendense.
Enterprise Block Archive is the Sendense repository engine for long-term VM protection. It reduces backup storage consumption through software-defined deduplication, compression and encryption, while keeping recovery points fast to browse, validate and restore.
9:1
Dedup potential
90%
External S3 reduction
0
Dedupe appliances
Up to 9:1 Deduplication
Reduce backup storage by storing shared VM data once and referencing it many times across recovery points.
Up to 90% Lower External S3 Footprint
EBA avoids writing duplicate data to external S3-compatible repositories, helping cut storage usage, duplicate writes and archive transfer overhead.
Immutability by Design
Retention, legal hold and controlled deletion workflows are built into the repository layer, not bolted on afterwards.
No Dedupe Appliance Required
EBA ships with Sendense, so efficient backup retention does not depend on specialist dedupe hardware.
Storage and cost savings vary by workload similarity, change rate, retention depth, encryption scope and external storage provider pricing.
True backup immutability, built into the foundations.
Many backup platforms make immutability an infrastructure project: build a hardened Linux repository, isolate it, patch it, monitor it and document it. EBA takes a cleaner path. Immutable retention is part of the Sendense repository layer.
Retention policy, legal hold, delayed deletion and audit history are managed together in the platform, helping teams protect recovery points without another hand-built repository island.
Immutable retention is managed inside Sendense, not left as a manual repository-hardening project.
Legal holds can preserve selected VMs, backups, repositories or wider estates with documented release controls.
Deletion workflows are controlled, delayed and auditable, helping protect recovery points from accidental or malicious removal.
External S3-compatible providers can be used for offsite retention where object-lock style protection is required.
Lower external S3 costs before the data lands.
EBA deduplicates before writing to external S3-compatible storage. When protected data already exists in the repository, Sendense references the existing data instead of writing another copy.
Lower Storage Footprint
Shared operating-system blocks, application binaries and unchanged data are stored once, helping reduce long-term archive capacity.
Fewer Duplicate Writes
Data already present in EBA does not need to be written again to external S3-compatible storage, helping reduce duplicate object-write activity.
Less Archive Transfer
By avoiding duplicate archive writes, EBA helps reduce the volume of data sent to external retention targets during backup operations.
How EBA works
EBA turns VM recovery points into efficient, protected repository data while keeping restore workflows practical for real incidents.
Capture
Sendense protects the workload and records the recovery point with the metadata needed for restore and validation.
Reduce
EBA identifies data already present in the repository, so common operating-system and application blocks do not need to be stored again.
Protect
Backup data is compressed, encrypted and written into the EBA repository with integrity and retention controls.
Recover
When recovery is needed, Sendense reconstructs only what is required for file browse, validation or full restore.
Fast restores without full archive rehydration.
Many archive systems must rebuild or rehydrate large backup images before recovery can begin. EBA is designed so Sendense can work directly from the recovery point, reading only the data needed for file browsing, validation or restore. That helps reduce recovery delays, especially for large VMs and long-retention repositories.
Scope: VM, backup, repository or full estate
Reason: Litigation, audit or incident preservation
Release: Controlled release with user, reason and timestamp
Audit: Every hold action recorded
Backups are not just stored. They are governed.
EBA gives recovery points a policy and evidence trail. Retention, legal hold, controlled deletion and audit history help teams show not only that backups exist, but that they were protected correctly.
Explore Sendense securityA Sendense repository first, with external S3 support when you need it.
EBA is built into Sendense as its own repository engine. It can be used for efficient on-platform backup retention, and it can also write to supported external S3-compatible storage providers for offsite retention, archive copies or cloud-based resilience.
Built for real backup estates
Immutable by design. Efficient by default.
EBA gives Sendense a repository foundation for deduplication, fast recovery, external S3 cost control and protected retention.