Restore tests, not a folder of hope
A backup that has never been restored is a guess. We schedule restore tests so you know the time to come back, who can run it, and what still sits outside the copy. The report is written so a director and an insurer can read the same page.
Retention that matches the risk
How long you keep a copy depends on the work, the law, and how far back you would need to rewind. We set retention on purpose: short enough to stay affordable, long enough that a quiet corruption does not eat every generation before you notice.
Ransomware recovery
If the live system is locked, the copy has to be out of reach of the same login. We separate the backup path, keep an offline or immutable generation where it belongs, and write the restore order before you need it. That is how an incident stays an incident, not a week of downtime.