# Backup restore validation system map | SourceX

Canonical: https://refer.sourcex.si/guides/backup-restore-validation-records-across-systems
Last updated: 2026-11-04

Following one restore validation case end to end takes four systems and four identifiers. Think of them as nodes in a small network: the backup console, the service desk, the document store for signed reports, and the client register. The identifiers that travel between them are the run ID, the incident number, the server name with its quarter, and the client code. Drop any one and a red result and a later green one sit side by side with nothing explaining the change.

This map is part of the [backup restore validation guide](/guides/workflow-backup-restore-validation). The [worked hard case](/guides/backup-restore-validation-exception-examples) tells one test as a story of decisions; this page is the wiring underneath it: which node holds what, which identifier leaves it, and who owns each node.

## Four nodes and what each one knows

Each node answers one question and none answers all of them. An export from the console alone is a list of runs and outcomes; the reasons live elsewhere.

**Backup console: what ran and what it returned.** Runs, session identifiers, boot and application outcomes. Its key out is the run or session ID. Note whether each outcome came from a full boot test or an integrity-only check, because they mean different things.

**Service desk or PSA: why someone acted.** The incident that diagnosed a red result and the change that altered scope, configuration or environment. Its keys out are the incident number and the change number with its close time.

**Document store: what the client accepted.** The signed quarterly or annual report, usually a PDF naming a quarter and a list of servers rather than individual runs. Its key is the server list.

**Client register: whose environment it was.** The client or tenant code that every other node should carry, plus the contract stating what is tested and how often. It keeps a renamed or acquired client from splitting into two.

## System map: record, linking key and owner

The table is the map in one view. Read across a row to see what each system contributes and which key reaches the next system.

| System | Record | Linking key out | Points to | Owner |
|---|---|---|---|---|
| Backup platform | Restore job and session | Job or session ID | Ticket body or related-record field | Backup team |
| Backup platform | Boot and application test result | Job ID plus server name | Same job; retest job | Backup team |
| Service desk | Incident ticket for the failed test | Ticket number | Change record's parent field | Service desk manager |
| Service desk | Change to test scope or environment | Change number and close time | Next retest job | Change approver, often the client |
| Document store | Signed restore validation report | Quarter and server list | Retest job for each server | Client approver; provider account lead |
| Client list | Client or tenant code and contract | Client code | Every record above | COO or contracts lead |

Two keys are typed by people rather than generated by systems: the job ID in the ticket and the server list on the report. Those are where joins break. Ask about them first.

## One fully joined case (Illustrative)

Illustrative and invented for this page. A fictional 260-person managed IT provider tests a client's ERP server. Here is what the same case looks like when every key holds.

| Key | Value | Found in | Joins to |
|---|---|---|---|
| Client code | DST-07 | Client list, all records | Contract that requires quarterly ERP restore tests |
| Job ID | RT-0412 | Backup platform; pasted into ticket | Ticket SD-11873 |
| Ticket number | SD-11873 | Service desk; parent field on change | Change CHG-2290 |
| Change number | CHG-2290, closed Mar 4, 15:05 | Service desk | Retest RT-0419, started Mar 5, 02:10 |
| Server and quarter | ERP app server, Q1 | Retest RT-0419; signed report | Client sign-off, Mar 6 |

Read top to bottom, the chain says: this client's contract required the test, the first run failed, a technician linked the failure to a ticket, the ticket led to an approved change, the change preceded a retest, and the client signed off on that retest. Remove the job ID from the ticket and the second row floats free. Remove the change close time and nobody can show the retest came after the fix.

## Chronology: normalize time before claiming order

A join is not enough; the order has to be provable. Backup platforms often log in server time while service desks record each user's local time, and a change that "closed before the retest" can turn out to have closed after it once both are put in one time zone.

NIST's log management guide names inconsistent timestamps across sources as a complication for anyone analyzing logs, and recommends keeping each logging host's clock synchronized to a common time source. For a reviewer, the practical questions are: which time zone does each system record, were the clocks synchronized, and did any system change time zones or vendors during the years covered? Those three answers go into the introduction note as plain words.

Retention is the other half of chronology. Note whether job history is kept for years or only for a rolling window, and whether older tickets survived a service desk migration. The [legacy export guide](/questions/export-data-from-legacy-system) covers what to ask when older history sits in a system the company plans to retire, and the [Azure DevOps work item history page](/systems/azure-devops-export-work-items-history) is an example of how revision history can survive or be lost in an export.

## Where joins break, and how to ask about each

Ask one yes-or-no question per key. Do not assume an export exists; ask the infrastructure director what each system can actually produce, and in what format.

- **Job to ticket.** "Do technicians paste the job or session ID into the ticket, or describe the failure in words?"
- **Ticket to change.** "Are changes raised from the ticket, so the parent field is filled, or from a template?"
- **Change to retest.** "Is a retest triggered by the change, or does the next scheduled run serve as the retest?"
- **Retest to sign-off.** "Does the signed report list servers and jobs, or only the quarter?"
- **Everything to the client.** "Has any client been renamed or merged, and did the client code survive?"

Tools also distinguish the kind of test behind each outcome: Veeam's documentation, for example, separates full recoverability testing, which boots machines from backup in an isolated lab, from a mode that only checks integrity and scans content. CISA advises testing both partial and full restores, so a provider may hold two families of records with different keys. Ask whether partial restore requests from users sit in the same service desk queue as scheduled tests. The [MSP ticket data page](/data-types/msp-ticket-data) describes neighboring ticket records, and the [email archive vs backup page](/systems/email-archive-vs-backup) explains why the backup copies themselves are not the record set under discussion.

Write the answers as metadata: years covered, rough volume, which keys hold. 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. Who can authorize a discussion, given that client records are involved, is covered on [who can license backup restore validation records](/questions/who-can-license-backup-restore-validation-records). Whether the joined records can be licensed stays unknown until SourceX's rights review.

## 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 the infrastructure director can say yes to most of the five join questions, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://helpcenter.veeam.com/docs/vbr/userguide/recovery_verification_surebackup_job.html
- https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-92.pdf
- https://www.cisa.gov/cyber-guidance-small-businesses
- https://refer.sourcex.si/terms
