THE PRESSURES
Pressures the backup program is operating under.
The backup target sits in the middle of the ransomware attack model, the cyber insurance review, and a budget that doesn't grow. The constraints don't come from one stakeholder. They show up at the same time.
THREAT
The backup is now the target.
Ransomware operators go after the backup repository first. Compromised admin credentials and hostile backup processes mean the recovery path is part of the attack model, not the escape hatch.
Complexity
Backup shouldn't need a specialist.
Mid-market IT doesn't carry a dedicated storage engineer. Multi-quarter integration projects aren't in scope. The target has to deploy in a day, run quiet, and recover without a runbook rewrite.
BUDGET
The target has to land inside what's already approved.
Mid-market IT runs on flat or modest growth. The backup refresh competes with everything else. Total cost over the cycle matters more than the line item on the PO.
TEAM
The team is already running flat out.
Backup admins also run patch cycles, helpdesk escalations, and the next migration. The target has to deploy in days, run quietly, and recover without a runbook rewrite.
THE SCALITY ANSWER
How the platform proves recoverability
Immutability.
Object Lock enforced at the storage layer. The retention policy holds under compromised admin credentials and hostile backup processes.
Recoverability.
Distributed erasure coding and self-healing under failure events. Recovery runs from the same platform that held the data, in the format the backup app already speaks.
Affordability.
Software-defined deployment on standard hardware. Starts at a 20TB single node, scales into multi-petabyte clusters without re-platforming the backup target.
Operability.
S3-native to the backup stack already in production. Non-disruptive upgrades, quiet telemetry, no daily babysitting.
deploy
What ARTESCA does in the working week, across the life of the target.
Three phases that span the life of a backup target. Each phase is what the team experiences, not what the marketing slide claims.
20 TB
1 Node
100s TB
3 Nodes
8.5 PB
6+ Nodes
Single-node entry, three-node production, six-node scale. From a 20TB starting footprint up through multi-petabyte clusters. Software-defined deployment on the hardware the team already chose.
- Software-defined; deploys on the team's hardware
- S3-native; full fidelity from day one
- Pre-integrated with leading backup apps
Telemetry, retention enforcement, upgrades-without-disruption, quiet day‑to‑day operation. The backup target doesn't ask for the team's attention until the team needs to ask something of it.
- Object-level immutability enforced by storage
- Retention and lifecycle policies as configuration
- Non-disruptive upgrades, no maintenance theater
Day 0
Hour 1 · Contained
Day 1 · Clean
Immutable copies the storage layer enforces, distributed erasure coding for durability, audit evidence the insurer wants to see. Recovery runs from the same platform that held the data.
- Object Lock holds under credential compromise
- Distributed erasure coding and self‑healing
- Multi-site replication for site loss scenarios
VALIDATED BACKUP ECOSYSTEM
Integrated with the backup stack the enterprise already runs.
Scality ARTESCA sits underneath the backup applications already in production. The recovery path doesn't require rebuilding the toolchain or changing the operator runbook.














