Back to production requirements

Snapshot restore → Point-in-time restore

Status: Complete — PDF runbook provided
Priority: Must have
Audience: SRE, security, platform


Terminology

WasNow
Snapshot restorePoint-in-time restore

Why it matters

Production Serverless search needs a disaster-recovery path that meets RPO and RTO. Focus recovery on the interactive Serverless dataset in Azure Central US.

Current state

ItemStatus
Azure Central USDelivered
Point-in-time restore runbookComplete — PDF provided

Multi-region restore remains a future enhancement and is not a blocker for Central US GA.

What was done

  1. Point-in-time restore runbook published (PDF) for the interactive Serverless plane in Azure Central US.
  2. Multi-region restore noted as future work.

Acceptance criteria

  • Point-in-time restore runbook published for Azure Central US (PDF)
  • RPO/RTO agreed for interactive Serverless indices (confirm with customer ops if not already locked)
  • Multi-region restore noted as future work
  • Restore drill planned or completed in Central US (optional follow-on)

Related

  • Azure Central US region (delivered)
  • Autosharding (restored indices should match production shard layout)