Preserving restore validation history before a backup vendor migration: a retention timeline

Short answer

Before a backup vendor migration, inventory the history of restore testing, not the backups: console session history, verification job reports, the tickets raised when a test failed, the change records that fixed it and the client's signed acceptance. Then put a date on each. Console history usually goes first, ending at decommission or earlier under its retention setting; tickets and signed sign-offs tend to outlast the switch. Whoever owns each record type decides whether anything is kept longer.

Visual briefFull-size diagram
A horizontal timeline from contract notice through parallel running, cutover and decommission, with four record lanes: console session history fades out at decommission unless exported, verification job reports end with the old server, while restore-test tickets and signed client sign-offs continue.
Illustrative timeline for one migration. Each company's dates come from its own contracts and retention settings.

This timeline is part of email archive vs backup for a client data inventory, which explains why backups are a poor long-term copy of records and where restore-test evidence lives. This page treats the migration as a clock: what to note, in which order, before each record type runs out.

Five dates that set the clock

A backup vendor migration is a sequence, not a day. Ask the client, or its MSP, for five dates from its own contracts and project plan:

  1. Notice date: when notice was given, or will be given, on the outgoing backup contract.
  2. Parallel start: when the new platform begins taking backups alongside the old one.
  3. Cutover: when the old platform stops taking new backups.
  4. Last restore point: the date after which the old platform's backups are no longer kept for recovery.
  5. Decommission: when the old server, appliance or tenant, and its database, is switched off.

The restore validation history lives mostly between dates 1 and 5. If no one can name date 5, that is the first finding: it means the console's history has no planned end, which in practice often means it ends without notice when hardware is reclaimed.

How long each restore validation record tends to last

Retention depends on product, configuration and the client's policy. The table gives the pattern and what to ask; it is not a statement about any one platform.

Record typeWhere it usually livesWhat ends itTends to last
Console session history (job runs, restore tests)Old backup server databaseRetention setting, then decommissionWeeks to a year, set per installation
Verification and test job reportsOld console, sometimes emailedSame as sessions; emailed copies follow mail retentionVaries; emailed copies often longest
Failed-test ticketsService desk or PSAService desk retention policyUsually years
Change records for the fixService desk or change logSame as tickets, if linkedUsually years
Signed client sign-offsDocument storeDocument retention policyUsually years
Restore test plans and schedulesShared drive or wikiOverwritten by new versionsCurrent version only, unless versioned

Session history is set per installation. In Veeam Backup & Replication, for example, session history retention can keep all sessions or keep only a set number of weeks, with outdated sessions removed by a background process. Where Veeam Backup Enterprise Manager is used, its retention values override the backup server's, and session data can be kept for between 1 and 53 weeks. Other platforms behave differently, so the right question is the actual setting, read from the console by the administrator.

What disappears first

Three things tend to go before anyone notices.

  • Detail older than the retention window. If sessions are kept for 13 weeks, a company with five years of quarterly restore tests holds detailed console evidence for about one of them. The rest exists only where someone copied it out.
  • The link between a test and its ticket. A failed restore test raises a ticket; the ticket often names the job but not the session. When the session is gone, the join depends on dates and job names typed by hand.
  • Superseded test plans. The plan that defined what a successful restore meant three years ago is overwritten by this year's version unless the document store keeps versions.

What survives is still worth describing. NIST's contingency planning guide expects backup media to be tested regularly and exercises to include recovery from backup media; a client that followed that practice for years holds a structured record of tests, exceptions and fixes, even if only the ticket and sign-off halves remain.

Illustrative timeline: one migration

A fictional 310-person regional accounting firm moves backups to a new platform. Its MSP has run quarterly restore tests since 2020.

DateEventRecord types affectedWho acts
Month 0Notice given on the old backup contractNone yet; inventory beginsIT director
Month 1Inventory complete: record types, years, owners, settingsAll, described at metadata levelMSP account manager with IT director
Month 2Parallel running startsNone lostMSP engineers
Month 3Cutover; new tests run on the new platformOld console stops gaining historyIT director
Month 6Last restore point on the old platform expiresOld backups no longer recoverableIT director
Month 7Old server decommissionedConsole session history and test reports end unless exportedIT director, with the client's approval

The firm's console kept 26 weeks of sessions, so detailed results reach back only to the start of the year. Tickets and signed sign-offs cover all five years. Month 1 is the step that matters: it gives the owners six months to decide, under their own policy, whether anything should be kept.

Who must approve keeping each record

Keeping a record past its normal life is the client's decision, made by the owner of that record and within its retention policy, contracts and privacy obligations.

Record typeWho can approve keeping itCheck first
Console session history and job reportsIT director or infrastructure headClient contracts covering hosted data
Failed-test tickets and change recordsIT director, with the service desk ownerPersonal data in ticket text
Signed client sign-offsThe client's own records ownerDocument retention schedule
Test plansIT directorUsually none

An MSP holding records for a client never decides this alone. The decision tree in who can license backup restore validation records shows who can say yes to a licensing discussion once the records are kept.

What the partner writes down

Answers, not records: the five dates, the session retention setting, which record types exist, the years each covers and who owns each one. The system map shows which keys join one restore test across the console, tickets and sign-offs, and the restore validation referral brief turns the notes into an introduction. For general advice on legacy exports, see exporting data from a legacy system and archiving versus backup; for the CIO's wider agenda in a sponsor-backed company, see the CIO of a private equity backed company.

The introduced company needs 50+ full-time employees at peak (contractors excluded), 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. Whether any restore history can be licensed stays unknown until SourceX reviews it.

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 a client has given notice on its backup platform and its decommission date is known, register as a partner, check the company against who qualifies and read the program terms before the old console is switched off.

  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

Is the cutover date when the restore history disappears?

Usually not. Cutover is when new backups start on the new platform. The old console's session history normally survives until the old server or tenant is switched off, or until its retention setting removes older sessions, whichever comes first.

Can the MSP export the old console's history on its own initiative?

It should not decide that alone. Keeping records past their normal life is the client's decision under its retention policy and contracts. The MSP can show the dates and ask the record owner whether anything should be kept.

Sources

  1. helpcenter.veeam.com/docs/vbr/userguide/history_settings.html
  2. helpcenter.veeam.com/docs/vbr/em/configuring_retention_settings.html
  3. nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800…
  4. refer.sourcex.si/terms

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