data-platform-disaster-recovery-and-business-continuity — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-platform-disaster-recovery-and-business-continuity (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when the question is how the data platform survives major failure, not only how one incident is handled. It helps agents design recovery objectives, backup and restore paths, control-plane recovery, failover decisions, and repeatable restore drills for data systems.
RTO and RPO for critical datasets or platform servicesDo not confuse incident handling with disaster recovery planning. Disaster recovery is the plan for major platform loss or sustained unavailability.
Identify:
Include:
RTORPOCover:
Options may include:
Run drills for:
| Rationalization | Reality |
|---|---|
| "The cloud provider already handles availability." | Provider uptime does not replace dataset restore, metadata recovery, or publish-safe failover design. |
| "We have backups, so we are covered." | Untested backups and undefined restore ownership do not prove business continuity. |
| "We can work out the failover steps during an outage." | Major outages are the worst time to discover recovery dependencies or missing permissions. |
RTO or RPO exists for critical data products~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.