Skip to content

Solutions

A runbook for the system you actually run.

Proving a backup means asking the right questions of the thing that was backed up. A till system, a virtual machine and a phone system are not proven the same way, so each gets a runbook written for it.

The library

What we can prove today

Each runbook knows how to back a system up and, more importantly, how to prove it came back. They run on the same agent and produce the same evidence; what differs is the questions each one asks.

Web hosting, Plesk servers, control panels

Plesk — encrypted offsite replication

For servers whose backups already leave the building, but leave it readable. Encrypted before it goes, filenames included, so whoever holds the storage holds nothing they can open — and part of it is decrypted nightly to prove it opens.

What it proves

  • A fresh backup exists, and is not a truncated stub
  • The offsite copy is encrypted before it leaves the server
  • Every file offsite matches what is on the server
  • The archive can still be decrypted with the key the server holds
  • Old copies are removed only after the new one is proven

Not seeing yours? That means a runbook has not been written for it yet — not that it cannot be. Most of this library started as somebody asking. Tell us what runs your business and we will tell you honestly whether we can prove it, and what that would take.

Tell us what runs your business.

Point of sale, ERP, phones, something nobody has heard of. We will tell you what proving it would look like — or say so if we cannot.

Ask about your system