Backup restore validation records: what a partner should bring to a company introduction

Short answer

A useful introduction about backup restore validation describes the records, not the data itself: which restore logs, integrity checks and client sign-offs exist, which systems hold them, how many years they cover, and who can authorize a licensing discussion. Restore tests that failed and were fixed are the most informative part, because they link an exception to an action and a checked outcome. Whether any of it can be licensed depends on rights, qualification and the proposed use.

Visual briefFull-size diagram
A four-day timeline of one illustrative restore test: the job reports success, the boot check passes, the application test fails because the domain controller was missing, a ticket and an approved change follow, the retest passes and the client signs off.
Illustrative restore test at a fictional managed IT provider. The record that matters is the gap between a green job and a working application.

Backup partners see this evidence every week, yet it rarely shows up in a data inventory. The archive vs backup comparison and the email archive vs backup page explain why backups are poor long-term records; this guide is about a different asset: the history of proving that restores actually work, and how to describe it in one page.

What is the backup restore validation task, in one sentence?

It is the routine of proving a backup can be restored into a working service, not just copied back. The introduction should open with that sentence written for the company's own practice, because "we run backups" and "we test restores and record the result" are different businesses.

CISA's ransomware guidance tells organizations to regularly test the availability and integrity of backups in a disaster recovery scenario, and its small-business guidance advises testing both partial and full restores. Tools draw the same line. Veeam's documentation, for example, separates a full recoverability test, which boots machines from backup in an isolated lab and tests them, from a mode that only checks backup integrity and scans content. A company that ran the first kind for years has a structured log of decisions; one that only ran the second has a thinner record. Asking which kind was run is the first question in the handoff.

The one-page handoff: seven fields

Seven facts, at metadata level: the task, the record types, the systems, the coverage, the exception pattern, the open question and the authorized contact. Fill them in from what the infrastructure director tells you, not from files you have seen.

Handoff fieldWhat to writeIllustrative entry
Business taskWhat a restore test proves and for whomQuarterly restore tests of client production servers, signed off by each client
Record typesLogs, checks, approvalsRestore job logs, boot and application test results, service desk tickets, change records, client sign-off forms
SystemsPlain-text tool names onlyBackup platform, service desk, document store for sign-offs
CoverageYears, volume, gapsAbout six years; roughly 1,900 test runs; sign-offs before 2021 kept as scanned PDFs
Exception patternThe hard case the records explainRestore completes but a key dependency is missing
Open questionWhat only a review can answerDo client contracts allow the provider to license test records about client systems?
Authorized contactRole of the person who can approve a licensing discussionCEO or owner, reached through the infrastructure director

Keep it to that page. The warm introduction brief covers how to frame the conversation with the owner; the handoff above is the operational half.

How to describe the exception without sharing the records

Name the pattern and the shape of its trail, in a sentence or two, and stop there. The pattern that makes restore history worth a review is the green job that hides a broken service.

In the Illustrative case in the graphic, a fictional managed IT provider runs a quarterly test on March 3. The restore job reports success and the boot check passes, but the application test fails because the domain controller the application depends on was not part of the restore. Veeam's documentation explains why this happens: a machine's dependent services, typically at least a domain controller, DNS and DHCP, must start first for verification to mean anything. A ticket links the job to the gap, a change adding the dependency is approved on March 4, the retest passes on March 5 and the client signs off on March 6.

In the handoff, that becomes one line: "Restore tests where the job succeeded but the application test failed, each with a ticket, a change and a retest; roughly how many per year." That tells SourceX the records connect an exception to an action and a checked result, without a single log line leaving the company.

Questions for the infrastructure director

Four questions fill the coverage and rights fields. Ask them, write down the answers, and leave anything uncertain marked as unknown.

  1. Coverage. Which years of restore tests can still be found, and in which systems? Were failed tests kept, or only the final pass?
  2. Volume. Roughly how many test runs, tickets and sign-offs per year?
  3. Rights. Do client contracts say anything about reuse of records describing client systems? Who would know?
  4. Authority. Who, above the director, could approve a licensing discussion if the company wanted one?

Those answers belong in the handoff as plain words. Do not ask for screenshots to "confirm" them.

Does the company qualify, and what stays unknown?

A company is worth introducing when the basics are met: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What you never collect: job exports, screenshots, sign-off forms, credentials or client names beyond what the owner chooses to share. What stays unknown until SourceX reviews it: whether buyers want restore validation records, what the rights review concludes about client-related content, what de-identification is needed, and any price. The MSP partner page and the MSP ticket data page cover neighboring record types, and ransomware-restored records covers what happens when a real restore, not a test, produced the data; the industries hub lists others. How rewards are calculated is on rewards.

Go deeper on backup restore validation records

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If an infrastructure director can fill the seven handoff fields, including the failed tests, register as a partner, check the company against who qualifies, and read the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does a company need perfect restore records to be worth introducing?

No. Gaps are normal, and SourceX reviews what exists. What helps is knowing which systems hold the records, how many years they cover, and whether failed tests were documented as carefully as passed ones.

How long should the introduction note be?

One page. The seven handoff fields on this page fit on a single screen, and anything longer usually means the partner has started describing data they should not have seen. The company adds detail itself after it applies.

Should I send SourceX a sample restore report?

No. Partners never collect or forward client records. Describe the record types, volume, date range and owning system in plain words, and let the company decide what to share after it applies.

Sources

  1. refer.sourcex.si/terms
  2. cisa.gov/sites/default/files/2025-03/StopRansomware-G…
  3. cisa.gov/cyber-guidance-small-businesses
  4. helpcenter.veeam.com/docs/vbr/userguide/recovery_verification_sur…
  5. helpcenter.veeam.com/docs/vbr/userguide/application_group.html

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment