Pattern A: Core Demo
Start here. A fast, low-cost demo that backs up a VM and a file share, then restores a lost file — proving recovery works in about 10 minutes.
A compact landing page for the four backup patterns, business click-through demos, published deployment artifacts, and the minimum decisions needed before moving from demo to production.
Use this as the front door for Azure Backup conversations: start with a business demo, open the matching deployment guide, then use the spec and KQL files as evidence for readiness, cost, restore testing, and governance.
Start with the app, file, or data set the business needs back first.
Choose vault, retention, owner, and recovery expectation.
Open the matching business demo and validate the recovery path.
Use guide, spec, KQL, and source links for production readiness.
Start here. A fast, low-cost demo that backs up a VM and a file share, then restores a lost file — proving recovery works in about 10 minutes.
For security teams. Shows how soft delete, RBAC, and alerts keep clean, recoverable backups even during a ransomware or insider attack.
For modern apps. Helps you choose the right vault for each workload by balancing recovery speed, depth, risk, and cost.
For the enterprise. Turns backup into a governed program with clear owners, guardrails, cost visibility, restore evidence, and audit-ready proof.
Recovery Services vault for VM, Azure Files, SQL in VM, SAP HANA, and hybrid. Backup vault for disk, blob, AKS, and newer operational backup scenarios.
Define RTO, RPO, retention, restore-test cadence, owner, evidence location, and cost owner before deploying production policy.
Use least privilege, soft delete, diagnostics, alerting, restore-test evidence, and immutability only where teardown and governance are understood.
| Pattern | Deployment | Spec | KQL | Source |
|---|---|---|---|---|
| A Core Demo | pattern-a-core-demo-deployment.md | SPEC.md | backup-jobs / failed / vault | GitHub |
| B Ransomware | pattern-b-ransomware-resilience-deployment.md | SPEC.md | failures / rbac / soft delete | GitHub |
| C Modern Apps | pattern-c-modern-workload-protection-deployment.md | SPEC.md | coverage / restore SLA / redundancy | GitHub |
| D Enterprise | pattern-d-enterprise-landing-zone-deployment.md | SPEC.md | budget / audit / cost / SLA | GitHub |
| Workload | Business service, data classification, owner, and recovery impact. |
|---|---|
| Vault | Recovery Services vault, Backup vault, or workload-native backup. |
| Policy | Frequency, retention, instant restore, redundancy, immutability, and timezone. |
| Restore | File, disk, VM, share, snapshot, point-in-time, or application-level path. |
| Evidence | Protected item, recovery point, test result, alert, KQL output, and owner signoff. |
| Cost | SKU, redundancy, retention, restored-resource lifecycle, and cleanup tags. |