What to restore
Identify data, configuration and dependencies needed for service.
RESILIENCE
Recovery planned around your deployment
Define dependencies, recovery objectives and a practical restore procedure. A backup is useful only when restoration is understood and tested.
Evidence snapshot: 2026-10-22 · review by 2026-11-22 · partial_read_only
THE PRACTICAL TASK
What to agree for your team
How to restore
Document the sequence and access required by responsible operators.
How to verify
Run an authorized restoration exercise and record the result.
From requirements to a pilot
- 01
Map dependencies
- 02
Agree recovery objectives
- 03
Test restoration
- 04
Update the runbook
Controls
Backup and restoreNot verified
Backup and restore behavior is defined by the specific deployment profile.
No complete production restore drill evidence.Technical evidence
- Scope
- deployment_specific
- Evidence
- docs/enterprise/backup-restore-drill.md
Deployment profiles
SaaSBeta
A Wicsora-managed deployment with no published HA or SLA guarantee.
Current single-site runtime is not HA/SLA evidence.Technical evidence
- Region
- deployment_specific
- Evidence
- docs/enterprise/deployment-profiles.md
On-PremBeta
Customer-environment packaging with outbound access denied by default.
Signed artifacts and a customer restore drill are still required.Technical evidence
- Region
- customer_environment
- Evidence
- docs/enterprise/deployment-profiles.md;deploy/onprem
Evidence snapshot: 2026-10-22 · review by 2026-11-22 · partial_read_only