How long you can afford to be down before a restore has to be finished.
Recovery time objective (RTO) is the maximum amount of time you can tolerate between a disaster and being back at work — measured from failure to fully restored.
RPO and RTO are the two sides of a backup plan. RPO answers: how much data can you afford to lose? RTO answers: how long can you afford to be down? RTO is usually constrained by bandwidth and file count, not backup software cleverness. A full restore of a 2 TB photo archive over gigabit fiber takes roughly five to six hours of wall-clock time — that is the download, not the backup tool. On a 100 Mbps home connection the same restore is closer to two days.
For most creators and professionals, the realistic RTO is shaped by what you need right now, not by the full archive. You usually do not need all 2 TB before you can work again; you need the one Final Cut library and the one client folder. That is why granular restore and priority queueing matter as much as raw throughput — a useful RTO means “back at work,” not “every last byte in place.”
In macup, the restore browser lets you stream the files you need first while the rest pulls in the background. A photographer can usually reopen the current shoot’s Lightroom catalog in under an hour, even while the full archive is still downloading.