VMware Site Recovery Manager: Install, Configure, Manage [V8.2] — Lesson 3: Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback

Learning Objectives

• Translate a realistic infrastructure or application requirement into an executable approach for Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback.
• Use recovery-plan test evidence and timing report to verify configuration, connectivity, security, and expected behavior.
• Explain how to recover safely when a test bubble accidentally connected to a production network occurs.

Detailed Topics

• Protection groups
• Recovery plans
• Priorities
• Dependencies
• IP customization
• Test networks
• Test recovery
• Cleanup
• Planned migration
• Reprotect
• And failback
• Decision ownership, prerequisites, and acceptance evidence for Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback, narrating each decision and showing how it contributes to a tested Site Recovery Manager 8.2 solution with correctly paired sites, protected workloads, recovery plans, documented failover behavior, and repeatable recovery operations. The demonstration records recovery-plan test evidence and timing report so learners can compare design intent with observable behavior.

Hands-On Exercise

Configure and test Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback with representative infrastructure or application data. Use “a test bubble accidentally connected to a production network” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete recovery-plan test evidence and timing report for review.

1. Define the requirement and identify dependencies before changing the environment.
2. Create a baseline result that can be compared with later changes.
3. Reproduce the exception and test one hypothesis at a time.
4. Complete the evidence record and obtain peer or instructor review.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how recovery-plan test evidence and timing report should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback. Preserve the failing example, review recovery-plan test evidence and timing report, and verify whether “a test bubble accidentally connected to a production network” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The scope of Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback is clear, including what is deliberately excluded from the test.
• Evidence in recovery-plan test evidence and timing report supports each material decision and outcome.
• A negative test demonstrates that controls reject or expose an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply Protection groups, recovery plans, priorities, dependencies, IP customization, test networks, test recovery, cleanup, planned migration, reprotect, and failback, explain the decisions made, and defend the result with recovery-plan test evidence and timing report.