The backup storage that grows in tiers: performance, capacity and archive tier — the capacity managed by policy, not by hand.
The SOBR unites several repositories into a tiered logical pool: a performance tier for the recent backups (and the fast restores), a capacity tier on object storage for the history, an archive tier for the ice. The data moves by itself per policy: the capacity is governed, not chased on weekends.
How many 'hot' days the restores really need: the fast tier tuned on operations, not on anxiety.
Move vs copy, windows and thresholds: the rules written well make the storage infinite.
Hardened locally + Object Lock in the cloud: all the tiers armored.
The growth observed in Veeam ONE: the new extent before saturation, not after.
The Scale-Out Backup Repository unites several repositories in a pool with placement policies: the performance tier receives the backups (fast local extents), the capacity tier offloads to object storage (copy for the 3-2-1, move for the lifecycle), the archive tier freezes onto Glacier/Archive for years; the offload is native, the object storage's immutability (S3 Object Lock) adds up, the loss of an extent doesn't stop the pool: the backup storage that grows without migrations.
Years of history at decreasing cost.
The backup storage that scales with the data.
From seven scattered repositories to one governed pool.