Home » VMware » 2V0-621 v.2 » What are two potential causes for this?
When attempting to place a datastore in Maintenance Mode, the task remains at 1%.
What are two potential causes for this? (Choose two.)
A. Storage DRS is disabled on one or more virtual machine(s) disk(s).
B. Storage DRS rules prevent migration recommendations for the disk.
C. Storage DRS datastores have insufficient space to accommodate failover.
D. Storage DRS provisioning network has been limited with I/O control policies.
Correct Answer: AB
Explanation/Reference:
Explanation:
Datastore Cannot Enter Maintenance Mode
You place a datastore in maintenance mode when you must take it out of usage to service it. A datastore enters or leaves maintenance mode only as a result of a user request.
Problem
A datastore in a datastore cluster cannot enter maintenance mode. The Entering Maintenance Mode status remains at 1%.
Cause
One or more disks on the datastore cannot be migrated with Storage vMotion. This condition can occur in the following instances.
• Storage DRS is disabled on the disk.
• Storage DRS rules prevent Storage DRS from making migration recommendations for the disk.
Solution
• If Storage DRS is disabled, enable it or determine why it is disabled. See Storage DRS is Disabled on a Virtual Disk for reasons why Storage DRS might be disabled.
• If Storage DRS rules are preventing Storage DRS from making migration recommendations, you can remove or disable particular rules. a. In the vSphere Client inventory, right-click the datastore cluster and select Edit Settings. b. Select Rules and click the rule. c.Click Remove. d.Click OK.
• Alternatively, if Storage DRS rules are preventing Storage DRS from making migration recommendations, you can set the Storage DRS advanced option
IgnoreAffinityRulesForMaintenance to 1. a.In the vSphere Client inventory, right-click the datastore cluster and select Edit Settings. b.Select SDRS Automation and click Advanced Options. c.Enter 1 in the Value column for IgnoreAffinityRulesForMaintenance. d. Click OK.
Reference:
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-91D4FBBC-0677-44DA-B0F243A3504F8CA0.html