Concept
Recovery Points
How Sendense represents available points in time for restore, browsing, and recovery workflows.
Definition
A recovery point is a protected VM or workload captured at a specific point in time and stored in EBA. It is how operators choose what point in time to recover from.
Recovery points are created by protection patterns and carry their own health, location, retention, and governance state.
What a Recovery Point Represents
- A protected VM or workload at a specific point in time.
- The locations where that point is available for recovery.
- The restore readiness of each location.
- Retention and governance state.
- Validation or verification evidence where available.
- The operations available from that point, such as restore, browse, file recovery, deletion, or legal hold review.
Recovery Point Health
A health warning is not data loss
A recovery point health warning means Sendense wants verification or attention before restore. It is not, by itself, proof that backup data is lost.
Recovery Point Locations
A recovery point can have more than one location: its primary EBA repository, and a secondary-copy location where a secondary copy is configured.
Each location has its own health and restore eligibility, and a recovery point may be retained, expired, soft-deleted, or pending cleanup at a given location.
Locations do not always have identical capabilities. Repository health, immutability, legal hold, provider capability, and deletion state all affect which actions are available.
Available Actions
- Full VM restore.
- File-level recovery.
- Application item recovery where supported and indexed.
- Recovery validation.
- Download or restore-to-server for selected files.
- Legal hold review.
- Deletion queue or cleanup review where you have permission.
Only valid actions are shown
The GUI exposes the actions that are valid for the recovery point, its location, your role, and its current governance state.
Relationship to Protection Patterns
Protection patterns create recovery points and control how long they are retained.
A recovery point does not own its schedule or retention policy. It reflects the outcome of the pattern that created it, together with EBA repository state, validation state, and governance state.
Important Distinctions
- A recovery point is not a replication target or a Sendense Controller — those belong to DR replication, not backup.
- A recovery point is not just a file or object in storage. It is the recoverable outcome, with health, locations, retention, and governance attached.
- Not every recovery point can always be restored — health, location state, and governance decide what is possible right now.
Related Docs