ARTESCA

Usable backup capacity: Compare quotes on equal terms

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:07:05 GMT

Three quotes for the same backup repository arrive with three different capacity figures, and none of them mean the same thing. One states raw capacity, one states usable capacity after a protection scheme the quote does not name, and one states an effective figure that already assumes a data reduction ratio. Compared as printed, the cheapest per terabyte is usually the one that counted most generously, not the one that delivers most.

Immutable retention costs: Why deleted jobs use space

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:06:27 GMT

A backup job is deleted after a workload is decommissioned, and the capacity chart does not move. The restore points that job produced are still present, still locked, and still counted against the repository. Nothing in the backup console shows them any more, because the console lists jobs and this data no longer belongs to one. The space comes back when the lock expires, not when the decision to stop protecting the workload was made.

Backup retention costs: What another year really adds

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:05:48 GMT

A request to extend backup retention from one year to two is usually costed by doubling something. The instinct is understandable, since retention is expressed in time and time is linear. Storage consumption is not. What a twelfth extra month adds depends on what is actually sitting in the retained set at that depth, how well it still deduplicates against everything around it, and whether the copies are locked against deletion.

Cloud vs. on-prem backup: Price the recovery scenario

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:05:08 GMT

Cloud and on-premises backup storage are almost always compared on what it costs to keep data: a price per terabyte per month against a capital purchase spread over a few years. That comparison is tractable, which is why it gets made. It also describes the quiet years. The difference between the two models shows up on the day the data has to be read back, and that day is the one the platform exists for.

Backup storage costs: Build a three-year budget

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:04:30 GMT

A three year backup storage budget that consists of one purchase price and two years of silence will be wrong, and the error usually surfaces as an unplanned request rather than a forecast. Three years is the common horizon because it matches support terms and internal depreciation schedules, but the three year number is not the first year number multiplied by three. The line items behave differently over time, and several of the largest ones never appear on a quote at all.

Backup storage sizing: Budget for growth and churn

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:03:52 GMT

A first pass at backup storage sizing produces a number that is correct for the estate as it stands today. The platform, though, is bought for a period of years, and almost nothing about the estate holds still across that period. The gap between the sized number and the purchased number is a judgment about growth and churn, and it is usually settled by adding a round percentage that nobody can defend when it turns out to be wrong.

Backup storage refresh: Expand or replace?

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:03:11 GMT

A backup storage refresh rarely announces itself as an architecture decision. It arrives as a support renewal quote with a date on it, and the choice gets made against that date: extend the existing platform, or replace it. The quote is a real input, but it prices one year of one line item. What it does not describe is data layout, migration effort, or how long the old system has to stay powered because of locks already written to it.

Backup storage procurement: Compare complete solutions

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:02:35 GMT

Three quotes arrive for backup storage and each one prices something slightly different. One states raw capacity, another states capacity after a data reduction assumption, and the third includes three years of support where the others include one. Ranking them on the bottom line produces an answer, but not a reliable one, because the numbers being ranked do not describe the same thing.

Backup storage power and rack costs: What to include

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:01:47 GMT

Two backup storage options are compared on hardware and software, a decision is taken, and the equipment arrives in a room somebody else pays for. The rack units it occupies, the power it draws, the heat it adds and the switch capacity behind its ports are all real costs. In a colocation contract they appear as line items. In an owned room they are usually invisible, which is not the same as absent.

Backup storage headroom: How much should you budget?

joshua.silvia@scality.com (Joshua Silvia) — Sun, 20 Sep 2026 04:01:09 GMT

Headroom on a backup repository is usually a round proportion, carried over from the last platform or from whatever the previous administrator wrote down. It survives because nothing tests it until the week it fails. The figure has a specific job, though. It has to absorb the next full, a retention change nobody costed, a restore staged back onto the same platform, the capacity a rebuild consumes, and the weeks between deciding to buy and racking the result.