data-platform-disaster-recovery-and-business-continuity

Name: data-platform-disaster-recovery-and-business-continuity
Author: vaquarkhan

19stars4forks

How to install data-platform-disaster-recovery-and-business-continuity?

vaquarkhan/data-engineering-agent-skills/data-platform-disaster-recovery-and-business-continuity

$npx -y skills add vaquarkhan/data-engineering-agent-skills --skill data-platform-disaster-recovery-and-business-continuity

Installs into the current project.

Summary

Guides agents through disaster recovery and business continuity planning for data platforms. Use when defining region or account failover, backup and restore, RTO or RPO targets, control-plane recovery, or restore drills for pipelines, warehouses, lakehouses, and publish surfaces

Files · 1

View on GitHub

SKILL.md

1	# Data Platform Disaster Recovery And Business Continuity
2
3	## Overview
4
5	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.
6
7	## When to Use
8
9	- defining `RTO` and `RPO` for critical datasets or platform services
10	- planning region, account, or environment failover
11	- validating backup and restore behavior for warehouses, lakes, or stateful processors
12	- designing business continuity for shared data products and critical publish paths
13	- running recovery drills before a real outage forces them
14
15	Do not confuse incident handling with disaster recovery planning. Disaster recovery is the plan for major platform loss or sustained unavailability.
16
17	## Workflow
18
19	1. Classify the critical services and data products.
20	Identify:
21	- critical datasets
22	- control-plane dependencies
23	- orchestration and metadata services
24	- downstream consumer and business impact
25
26	2. Define recovery objectives.
27	Include:
28	- `RTO`
29	- `RPO`
30	- acceptable degraded mode
31	- mandatory publish protections during failover
32
33	3. Map recovery assets and dependencies.
34	Cover:
35	- backups and snapshots
36	- checkpoint or incremental state
37	- orchestration definitions
38	- secrets and access paths
39	- lineage and metadata services
40	- validation and reconciliation controls after restore
41
42	4. Choose the recovery strategy.
43	Options may include:
44	- restore in place
45	- warm standby
46	- cold standby
47	- cross-region or cross-account failover
48	- consumer-facing degraded mode with blocked publish
49
50	5. Prove the recovery path.
51	Run drills for:
52	- restore time
53	- checkpoint continuity
54	- publish blocking and reopen criteria
55	- reconciliation after restore
56	- ownership and escalation behavior
57
58	## Common Rationalizations
59
60	\| Rationalization \| Reality \|
61	\| --- \| --- \|
62	\| "The cloud provider already handles availability." \| Provider uptime does not replace dataset restore, metadata recovery, or publish-safe failover design. \|
63	\| "We have backups, so we are covered." \| Untested backups and undefined restore ownership do not prove business continuity. \|
64	\| "We can work out the failover steps during an outage." \| Major outages are the worst time to discover recovery dependencies or missing permissions. \|
65
66	## Red Flags
67
68	- no named `RTO` or `RPO` exists for critical data products
69	- backup inventory ignores metadata, orchestration, or incremental state
70	- failover is described without validation or reconciliation after restore
71	- publish behavior during degraded mode is undefined
72	- recovery drills have never been executed
73
74	## Verification
75
76	- [ ] Critical data products and services have explicit recovery objectives
77	- [ ] Backup, restore, and dependency recovery paths are documented
78	- [ ] Recovery strategy matches business impact and platform constraints
79	- [ ] Restore drills validate time, correctness, and publish protection
80	- [ ] Ownership and escalation paths are clear during major outage scenarios

People who liked this also viewed

6 picks

Type

data-platform-disaster-recovery-and-business-continuity

19stars4forks

View on GitHub

How to install data-platform-disaster-recovery-and-business-continuity?

vaquarkhan/data-engineering-agent-skills/data-platform-disaster-recovery-and-business-continuity

$npx -y skills add vaquarkhan/data-engineering-agent-skills --skill data-platform-disaster-recovery-and-business-continuity

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Data Platform Disaster Recovery And Business Continuity
2
3	## Overview
4
5	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.
6
7	## When to Use
8
9	- defining `RTO` and `RPO` for critical datasets or platform services
10	- planning region, account, or environment failover
11	- validating backup and restore behavior for warehouses, lakes, or stateful processors
12	- designing business continuity for shared data products and critical publish paths
13	- running recovery drills before a real outage forces them
14
15	Do not confuse incident handling with disaster recovery planning. Disaster recovery is the plan for major platform loss or sustained unavailability.
16
17	## Workflow
18
19	1. Classify the critical services and data products.
20	Identify:
21	- critical datasets
22	- control-plane dependencies
23	- orchestration and metadata services
24	- downstream consumer and business impact
25
26	2. Define recovery objectives.
27	Include:
28	- `RTO`
29	- `RPO`
30	- acceptable degraded mode
31	- mandatory publish protections during failover
32
33	3. Map recovery assets and dependencies.
34	Cover:
35	- backups and snapshots
36	- checkpoint or incremental state
37	- orchestration definitions
38	- secrets and access paths
39	- lineage and metadata services
40	- validation and reconciliation controls after restore
41
42	4. Choose the recovery strategy.
43	Options may include:
44	- restore in place
45	- warm standby
46	- cold standby
47	- cross-region or cross-account failover
48	- consumer-facing degraded mode with blocked publish
49
50	5. Prove the recovery path.
51	Run drills for:
52	- restore time
53	- checkpoint continuity
54	- publish blocking and reopen criteria
55	- reconciliation after restore
56	- ownership and escalation behavior
57
58	## Common Rationalizations
59
60	\| Rationalization \| Reality \|
61	\| --- \| --- \|
62	\| "The cloud provider already handles availability." \| Provider uptime does not replace dataset restore, metadata recovery, or publish-safe failover design. \|
63	\| "We have backups, so we are covered." \| Untested backups and undefined restore ownership do not prove business continuity. \|
64	\| "We can work out the failover steps during an outage." \| Major outages are the worst time to discover recovery dependencies or missing permissions. \|
65
66	## Red Flags
67
68	- no named `RTO` or `RPO` exists for critical data products
69	- backup inventory ignores metadata, orchestration, or incremental state
70	- failover is described without validation or reconciliation after restore
71	- publish behavior during degraded mode is undefined
72	- recovery drills have never been executed
73
74	## Verification
75
76	- [ ] Critical data products and services have explicit recovery objectives
77	- [ ] Backup, restore, and dependency recovery paths are documented
78	- [ ] Recovery strategy matches business impact and platform constraints
79	- [ ] Restore drills validate time, correctness, and publish protection
80	- [ ] Ownership and escalation paths are clear during major outage scenarios

People who liked this also viewed

6 picks

Type