Soteria Cloud KB

10.60 — Disaster Recovery

Disaster Recovery

Coverage

  • Service prerequisites, supported workloads and limitations

  • Recovery-server and primary-server models

  • Cloud networks, IP addressing, routing, DNS and DHCP

  • Site-to-site and point-to-site VPN design

  • Public IP and connectivity dependencies

  • Protection-plan/DR-plan relationship and RPO/RTO

  • Runbooks, dependencies and startup order

  • Test failover, isolated testing and evidence

  • Production failover authorisation and execution

  • Failback, data synchronisation and return to production

  • Health monitoring, alerts, reports and capacity

  • DR troubleshooting and Acronis/Soteria escalation

Runbook minimum

Every protected service needs owner/approver, protected workload, dependency map, recovery objective, network mapping, credential/secret handling process, validation test, failover decision point, communications plan and failback steps.

Existing SCKB guidance

A live production failover is a controlled service action, not a generic self-help step.

<!-- SCKB-PORTFOLIO-BASELINE-START -->

Portfolio-baseline operational pages

Published 21 August 2026. These Soteria-original operational pages define scope, qualification, service boundary, evidence and escalation, with canonical Acronis sources. They do not mean that every article-level procedure in the 5,790-URL English source register has been migrated.