Getting started with cloud-based cleanroom recovery includes defining where workloads are recovered, how they are grouped, and how recovery is executed. You can use this configuration for both recovery testing and incident response.
Key components
Cleanroom recovery uses the following components:
-
Cleanroom site: The isolated environment where recovered workloads run. The site is created automatically or selected when you create a runbook.
-
Recovery group: A collection of workloads that are recovered together.
-
Runbook: The sequence of actions that controls how recovery is performed, including where workloads are recovered and in what order.
Best practices
-
Align cleanroom networking and configuration with your production environment to ensure meaningful validation.
-
Define recovery groups based on application dependencies, not infrastructure boundaries.
-
Separate foundational services, such as Active Directory, into dedicated recovery groups and validate them before recovering dependent workloads.
-
Group application components that must be validated together, such as application servers and their supporting databases.
-
Specify a recovery order that reflects real application startup behavior so workloads are recovered in a functional and testable state.
-
Review and update recovery groups and runbooks as applications and dependencies change.