VMware Site Recovery Manager: Install, Configure, Manage [V8.6] — Lesson 3: Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery.
• Complete a controlled activity for Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery and capture recovery-plan test report and sequence evidence.
• Challenge the result with a dependent application service starting before its database is ready, then justify the corrective action.

Detailed Topics

• Recovery plans
• Priorities
• Dependencies
• IP customization
• Scripts
• Test networks
• Isolated test recovery
• Cleanup
• Planned migration
• And disaster recovery
• Decision ownership, prerequisites, and acceptance evidence for Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery from requirement through execution and review. Learners see where evidence should be collected, how recovery-plan test report and sequence evidence supports validation, and which warning signs require investigation.

Hands-On Exercise

Work through a role-based scenario involving Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery. Validate the expected path, test “a dependent application service starting before its database is ready,” choose the safest corrective action, and capture the reasoning and outcome in recovery-plan test report and sequence evidence.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

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

Troubleshooting Guidance

When Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect recovery-plan test report and sequence evidence, test whether “a dependent application service starting before its database is ready” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• Configuration and source state used for Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery are versioned or otherwise traceable.
• Recovery-plan test report and sequence evidence shows both baseline and accepted result.
• Security, performance, dependency, and resilience side effects are considered where relevant.
• Recovery steps and handover notes are usable by an operations practitioner.

Lesson Outcome

Learners can apply Recovery plans, priorities, dependencies, IP customization, scripts, test networks, isolated test recovery, cleanup, planned migration, and disaster recovery, explain the decisions made, and defend the result with recovery-plan test report and sequence evidence.