# Who can license restore test records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-backup-restore-validation-records
Last updated: 2026-11-04

Introduce the CEO of the managed IT provider or company, who can authorize a data discussion, and name the infrastructure director as the person who knows the records. The director can say which restore logs, integrity checks and client sign-offs exist, but console access to a backup platform is not authority to license what it holds. When records describe client systems, client contracts and counsel join the path.

This decision tree is part of the [backup restore validation guide](/guides/workflow-backup-restore-validation). It turns the authority question into five yes-or-no branches a partner can work through in one conversation, so the right person is in the room before SourceX's rights review begins.

## Two people, two questions: who knows and who decides

The person who knows the records is rarely the person who can say yes to licensing them. Introductions stall when the two are confused.

**The person who knows.** The infrastructure director, sometimes titled head of infrastructure, backup and recovery lead or service delivery director, knows what is tested, how often, which systems hold the results, whether failed tests were kept and when an old backup platform will be switched off. They are the natural sponsor.

**The person who decides.** The CEO, who can authorize a licensing discussion and sign for the company. In a managed IT provider of a few hundred people, the COO or managing director often sponsors it, advised by general counsel or a contracts lead; in a company that tests its own systems in-house, the CIO or CFO usually does.

A useful line to the director: "If the company wanted to explore licensing these records, who would need to agree?" The answer names the second person.

## The decision tree

Work down the branches in order. Each answer either adds a person to the introduction or moves you to the next question.

| Branch | Question | If yes | If no |
|---|---|---|---|
| 1 | Do the restore records describe only the company's own systems? | Go to branch 3 | Go to branch 2 |
| 2 | Do they describe client systems, as in a managed IT provider? | Add general counsel or the contracts lead; client agreements may require consent or exclusion | Go to branch 3 |
| 3 | Do tickets, changes or sign-offs name individual technicians or client staff? | Expect privacy review; note it, do not resolve it | Go to branch 4 |
| 4 | Has the director agreed to bring in the CEO, who can authorize a licensing discussion? | Go to branch 5 | Ask the director how to reach the CEO; do not submit yet |
| 5 | Is the CEO willing to take an introduction? | Make the introduction, naming the director as the records contact | Wait; an introduction without the authorized contact will stall |

Two paths cover most real cases. An in-house IT team testing its own servers usually runs 1, 3, 4, 5. A managed IT provider almost always passes through branch 2, because its restore logs are about client infrastructure.

## Roles and what each can authorize

Titles below the CEO vary by company, so ask what each person knows and does rather than relying on the job name.

| Role | What they know | Can they authorize a licensing discussion? |
|---|---|---|
| Infrastructure director | Test scope, schedule, systems, retention, gaps | Usually not alone; the natural sponsor |
| Backup or platform engineer | Job configuration and export formats | No |
| Service desk manager | Ticket and change history, linking habits | No |
| COO or managing director | Business records, client contracts, priorities | No, but often sponsors the discussion |
| CEO | The company's records and contracts as a whole | Yes, and signs |
| General counsel or contracts lead | Client agreement terms on reuse and confidentiality | Advises; signs off on rights questions |
| The client | Its own systems and approvals in the records | Its contract may require consent or exclusion |

The client row is the one partners forget. In the [worked hard case](/guides/backup-restore-validation-exception-examples), the client's IT manager approved the change and accepted the report. That makes the client a participant in the record, not just its subject.

## Branches that need legal, client or privacy sign-off

**Client infrastructure.** A restore test of a client's ERP server records how that client's environment is built. Veeam's documentation notes that verifying a machine means starting the services it depends on first, typically a domain controller, DNS and DHCP. A test log therefore describes a client's core infrastructure, not just one server. Whether the provider may license that depends on the client agreement, and counsel reads it. The [MSP client onboarding questionnaire](/resources/msp-client-onboarding-questionnaire) and [offboarding checklist](/resources/msp-client-offboarding-checklist) show where those terms usually get set and unwound.

**Names and network details.** The European Commission describes personal data as any information relating to an identified or identifiable living individual, including a name or an IP address. Tickets carry technician and client staff names; logs can carry IP addresses. Privacy review is a normal step for this record set, not a warning sign.

**Partial restores.** CISA advises testing both partial and full restores. User-requested file restores often sit in the same service desk queue and may name the user and the file. Note that they exist; leave the rights question to review.

**Acquired providers.** Roll-ups often inherit several backup platforms and contract templates. Whether the buyer holds rights to an acquired provider's historical records is a question for its counsel. The [managed service providers page](/for/managed-service-providers) covers the wider partner context.

## What stays unknown until SourceX's rights review

The tree tells you whom to introduce. It does not decide what can be licensed. These stay open until SourceX reviews the opportunity with the company, as explained in [why data rights matter](/proof/why-data-rights-matter):

- whether the company holds the rights to license each record class
- what each client agreement permits for records about that client's systems
- what must be removed or de-identified, such as hostnames, IP addresses and names
- whether there is buyer interest, and on what terms

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license 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. Partners keep discovery at metadata level, never ask for logs, tickets or logins, and sign the Channel Partner Agreement before submitting introductions. The [records across systems map](/guides/backup-restore-validation-records-across-systems) lists which owner sits behind each system.

## 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.

Once the CEO, who can say yes to a discussion about the company's restore validation records, is willing to take the call, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the CEO.

## Sources

- https://refer.sourcex.si/terms
- https://commission.europa.eu/law/law-topic/data-protection/data-protection-explained_en
- https://helpcenter.veeam.com/docs/vbr/userguide/application_group.html
- https://www.cisa.gov/cyber-guidance-small-businesses
