---
title: Backups, Versioning & Recovery Context
slug: en/docs/backups-versioning-recovery
description: How Tenantial describes backups, versioning, and recovery context as support for cautious decisions without promising restore automation.
editUrl: false
lastUpdated: false
---

Backups and versioning are not an end in themselves in Tenantial. They create the context that helps teams understand which known state is protected and how defensively a recovery question should be evaluated.

## What this page covers

- why known states and versioning matter in governance work
- how recovery context should be separated from actual execution
- which buyer questions can be answered earlier through this framing

## Why versioning matters here

If teams no longer know which configuration state was last reviewed consciously, every change or recovery discussion becomes weaker. Versioning keeps those reference points readable.

## What recovery context means

Recovery context means that scope, known starting point, conflicts, and likely impact become understandable before a sensitive action is taken. The public story does not turn that into a promise of restore automation or a risk-free shortcut.

## Useful questions for buyers and reviewers

- Which known states should remain explainable for review or pilot work?
- Which differences make a recovery question relevant in the first place?
- Which roles need to understand scope and impact before a sensitive decision is made?

## Boundaries of this page

This page does not describe push-button restore and does not imply certain recovery outcomes. It only explains why known states and versioning can support more cautious decisions.

## Related links

- [Policy evidence](/en/docs/policy-evidence/)
- [Drift detection](/en/docs/drift-detection/)
- [Findings, exceptions & accepted risk](/en/docs/findings-exceptions-accepted-risk/)
- [Evaluation & pilot](/en/docs/evaluation-pilot/)