1.44 PB raw storage build
Veeam Standard Repository
Without appliance-class data reduction, a spinning repository has to scale close to the effective protected capacity.
Petabyte-scale effective backup capacity with fewer disks, fewer shelves and EBA included in the Sendense platform.
Veeam native data reduction can help, but large backup repositories often still force a choice: scale standard spinning disk or add a deduplicating appliance. Sendense EBA brings repository efficiency into the platform layer.
The savings compound as capacity grows: EBA adds commodity disk behind the same repository engine, while traditional designs keep expanding shelves or appliance spend.
92%
Lower Storage Cost
89%
Fewer HDDs
1.3mo
CSP Payback
Grows
With Scale
The 1.44 PB Proof Point
At 9:1 reduction, 160 TB raw becomes 1.44 PB effective. The model below compares three repository approaches against the same capacity target and shows why the gap widens as capacity increases.
1.44 PB raw storage build
Without appliance-class data reduction, a spinning repository has to scale close to the effective protected capacity.
160 TB appliance quote
A deduplicating appliance reduces the disk footprint, but the appliance cost becomes the expensive part of the design.
160 TB raw + NVMe tier
EBA is included with Sendense, pairing commodity disk with a mirrored NVMe performance tier and software-defined repository efficiency.
Capacity Model
Compare a standard spinning repository, a deduplicating appliance design and a Sendense EBA repository design using the same 9:1 data reduction assumption.
The important trend is not just the starting number. Moving from 720 TB to 1.44 PB effective capacity adds about £3,300 to the Sendense EBA repository design, compared with about £49,900 for the raw spinning repository model and £85,000 in the dedupe appliance quote path.
Effective Capacity
Assuming 9:1 dedupe and compression from 80 TB raw.
88%
Max Saving
88%
Vs Raw Repo
84%
Vs Appliance
89%
Fewer HDDs
Raw repository: 720 TB raw, 90 x 8 TB HDD, 8 disk shelves
Dedupe appliance: 80 TB dedupe appliance quote, assumed at 9:1
Sendense: 10 x 8 TB HDD + mirrored 3.2 TB NVMe tier
Rack footprint: about 88% fewer disk shelves than the raw spinning design.
Effective Capacity
Assuming 9:1 dedupe and compression from 160 TB raw.
92%
Max Saving
91%
Vs Raw Repo
92%
Vs Appliance
89%
Fewer HDDs
Raw repository: 1.44 PB raw, 180 x 8 TB HDD, 15 disk shelves
Dedupe appliance: 160 TB dedupe appliance quote, assumed at 9:1
Sendense: 20 x 8 TB HDD + mirrored 3.2 TB NVMe tier
Rack footprint: about 87% fewer disk shelves than the raw spinning design.
Scale Comparison
This compares the incremental Sendense EBA hardware step with two non-Sendense repository choices: a raw spinning repository build and a quoted dedupe appliance path.
Sendense EBA expansion
Sendense pathAdd another 720 TB effective capacity with 10 more 8 TB disks in the Sendense EBA repository design.
+£3.3k
Traditional raw repository expansion
External alternativeOutside Sendense, a non-deduplicating spinning repository needs another 720 TB of raw disk capacity.
+£49.9k
Dedupe appliance expansion
External alternativeOutside Sendense, the quoted appliance path moves from the 80 TB dedupe unit to the 160 TB unit.
+£85k
For a provider selling protected capacity every month, lower repository capex changes the service margin. At £5 per TB per month, repository payback can be measured in weeks rather than years.
The larger the service becomes, the more important this gets: protected capacity revenue scales linearly, but the Sendense repository cost curve stays much flatter than raw disk or appliance-led designs.
Capacity
720 TB effective
EBA Cost
£6,300
Revenue
£3,600/month
Payback
1.8 months
Capacity
1.44 PB effective
EBA Cost
£9,600
Revenue
£7,200/month
Payback
1.3 months
CSP revenue model uses effective protected capacity sold at £5/TB/month. It excludes support, power, server chassis, RAID/spare overhead, finance cost, software packaging and customer-specific operating costs.
Why Sendense EBA
The value is not only the first purchase. Fewer disks also means less power, less cooling, less rack space, fewer disk failures and less time spent designing around a specialist appliance.
Deduplication, compression, retention and direct recovery behavior are part of the Sendense repository path.
A mirrored SSD tier absorbs hot write behavior while capacity sits on commodity spinning disk.
Fewer HDDs and shelves reduce the number of moving parts in the repository estate.
CSPs can sell protected capacity without repository capex consuming the service margin.
Next Steps
How EBA reduces, accelerates and governs Sendense repository storage.
The broader comparison: storage, S3, open DR targets and migration.
Build BaaS and DRaaS services with storage economics that protect margin.
Review direct Sendense pricing and contact sales for MSP/CSP licensing.
Assumptions
These examples use stated assumptions so the repository economics are clear and customer-specific variables stay visible.
Veeam includes native compression and data reduction features, but that is not the same repository model as Sendense EBA. For appliance-class repository economics, Veeam estates often have to choose between scaling standard raw disk or adding a deduplicating storage appliance.
The comparison uses a 9:1 effective data reduction assumption across all scenarios. Actual results depend on workload similarity, operating systems, change rate, retention depth, encryption scope and backup policy.
The examples use Sendense repository design figures: 10 x 8 TB HDD with mirrored 3.2 TB NVMe tier at £6,300, and 20 x 8 TB HDD with the same NVMe tier at £9,600. EBA repository capability is included with Sendense.
EBA scales by adding commodity capacity behind the repository engine. Raw spinning repositories and dedupe appliances keep adding larger hardware blocks, so the cash, rack and power gap widens as protected capacity grows.
Share your current repository size, retention model, appliance quotes and target CSP price per TB. Sendense can model the storage, rack and payback difference.