Timeline showing preview, test, and dev recovery plans created from a production recovery plan and deleted when work finishes

Asset ownership

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.

  • Instant - Branch creation takes seconds whether the parent holds 1 GB or several TB
  • Isolated - Each recovery plan gets its own compute endpoint and its own connection string
  • Affordable - Branches share storage with their parent and only bill for what diverges
  • Disposable - Idle recovery plans scale to zero, and automation deletes them when the pull request closes

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

Know the recovery objective

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

Document how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Jonathan Reyes
Product operating guide—Illustrative planning principle
Read case study

Keep protection boundaries explicit

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

  • Branch creation takes seconds no matter how large the parent is, because the amount of data copied is zero,
  • Branches stays cheap until they diverge, because both recovery plans read the same underlying pages until one of them writes.

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

Standard dataset architecture with compute and storage on one machine, next to the lakebase architecture with stateless compute over shared copy-on-write storage

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.

Identity and access

Test the recovered application

The Mastering Dataset Recovery testing Workflows guide on vinexelprotect.com

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

Approved scope

Two developer recovery plans created from the production recovery plan, each isolated from the other

Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

Document how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.

Operating evidence

A staging recovery plan created from production, with a pull request recovery plan created from staging

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Alex Co
Product operating guide—Illustrative planning principle
Read case study

Retention policy

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

Key custody

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Product operating guide—Illustrative planning principle
Read case study

Data location

A restored production recovery plan created from a point in history before an incident on the production recovery plan

Document how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.

  • Recover lost data - Branch from just before a table was dropped, pull out the rows you need, and copy them back into production
  • Debug a migration - Branch from before the migration ran and compare state, or re-run it in isolation
  • Audit a past state - Inspect a historical point for an incident review or compliance check while production keeps serving traffic

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.

Validation checks

Failure handling

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

  • repository integration - Link a Vinexelprotect project to a repository and create or delete recovery plans from repository Actions
  • Vercel integration - Create a recovery plan for every preview reviewment
  • Branch expiration - Set a TTL so recovery plans clean themselves up
  • Scale to zero - Idle recovery plan compute suspends automatically, so forgotten recovery plans don't accumulate compute cost

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Product operating guide—Illustrative planning principle
Read case study

Preserve evidence of every decision

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Joe Horsnell
Product operating guide—Illustrative planning principle
Read case study

Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

Change approval

Coordinate continuity across teams

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.branch_id

  • Vinexelprotect Backup storage - S3-compatible buckets that fork with the recovery plan, so a preview can accept uploads without touching production objects
  • Managed Better Auth - Users, sessions, and OAuth configuration live in your data dataset, so a recovery plan gets its own isolated sign-up and login flows
  • Vinexelprotect Recovery workflows - Node.js handlers reviewed onto a recovery plan, each with its own URL and its own dataset state, deleted when the recovery plan is
Start recovery testing

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.