VMware vSAN: Management and Operations [V7] — Lesson 2: Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay

Learning Objectives

• Identify the architecture and operational choices that shape Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay.
• Run normal and boundary tests and record the outcome in maintenance execution record and compliance recovery test.
• Separate root cause from symptom when investigating maintenance starting without enough free capacity to complete evacuation.

Detailed Topics

• Policy assignment
• Compliance
• Maintenance modes
• Resynchronization
• Data evacuation
• Disk and host replacement
• Capacity reservations
• Slack space
• And repair delay
• Decision ownership, prerequisites, and acceptance evidence for Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay within a scenario aimed at a well-operated vSAN 7 service with controlled policies, capacity, maintenance, performance, health, fault response, upgrades, and support handover. The walkthrough contrasts a valid setup with a flawed one and uses maintenance execution record and compliance recovery test to make the difference explicit.

Hands-On Exercise

Configure and test Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay with representative infrastructure or application data. Use “maintenance starting without enough free capacity to complete evacuation” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete maintenance execution record and compliance recovery test for review.

1. Confirm scope, access, sample workloads, and acceptance criteria.
2. Perform the configuration or operation using a controlled sequence.
3. Inspect outputs and downstream effects rather than relying on task status alone.
4. Close with a support note, preventive action, and reproducible validation step.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how maintenance execution record and compliance recovery test should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect maintenance execution record and compliance recovery test, test whether “maintenance starting without enough free capacity to complete evacuation” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• The scope of Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay is clear, including what is deliberately excluded from the test.
• Evidence in maintenance execution record and compliance recovery test 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 Policy assignment, compliance, maintenance modes, resynchronization, data evacuation, disk and host replacement, capacity reservations, slack space, and repair delay, explain the decisions made, and defend the result with maintenance execution record and compliance recovery test.