This lesson examines Installing SRM, pairing sites, configuring array-based or vSphere Replication integration, inventory mappings, placeholder datastores, and protection groups within VMware Site Recovery Manager: Install, Configure, Manage [V8.6]. The work supports a tested Site Recovery Manager 8.6 implementation with correctly paired sites, protected workloads, ordered recovery plans, network mappings, failover evidence, and documented reprotection and uses observable evidence rather than assumption to judge readiness.
Using realistic infrastructure, identities, and workloads, the instructor demonstrates Installing SRM, pairing sites, configuring array-based or vSphere Replication integration, inventory mappings, placeholder datastores, and protection groups. Checkpoints are captured in paired-site configuration and protection-group validation, with discussion of alternatives, side effects, and acceptance conditions.
Build or execute Installing SRM, pairing sites, configuring array-based or vSphere Replication integration, inventory mappings, placeholder datastores, and protection groups for a defined scenario. Introduce the condition “placeholder virtual machines being created on a datastore unavailable to the recovery site,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in paired-site configuration and protection-group validation.
Avoid changing multiple settings at once while troubleshooting Installing SRM, pairing sites, configuring array-based or vSphere Replication integration, inventory mappings, placeholder datastores, and protection groups. Preserve the failing example, review paired-site configuration and protection-group validation, and verify whether “placeholder virtual machines being created on a datastore unavailable to the recovery site” is the root cause. After remediation, confirm downstream effects and add a monitoring action.
Learners can apply Installing SRM, pairing sites, configuring array-based or vSphere Replication integration, inventory mappings, placeholder datastores, and protection groups, explain the decisions made, and defend the result with paired-site configuration and protection-group validation.