What administrative tasks are needed to increase the capacity of the vVols datastore without the use of the VSI plugin?

Question

Options

• AChange the storage container quota in PowerStore Manager and refresh the datastore capacity in
• BChange the storage container quota in PowerStore Manager and restart the VASA service in
• CChange the datastore capacity in vSphere and restart the VAAI service in PowerStore Manager
• DChange the datastore capacity in vSphere and refresh the storage container quota in PowerStore

• A
  79% (30)
• B
  13% (5)
• C
  5% (2)
• D
  3% (1)

Explanation

Option A is correct because vVols datastore capacity is governed by the storage container quota on the PowerStore array - you must increase it in PowerStore Manager first, then trigger a capacity refresh in vSphere so vCenter picks up the new value; no service restarts are required.

Why the distractors are wrong:

• B is wrong because restarting the VASA service is disruptive and unnecessary - a simple datastore refresh is all that's needed after the quota change; VASA restarts are reserved for connectivity/registration issues.
• C is wrong on two counts: vVols datastore capacity cannot be changed from within vSphere (the array owns it), and VAAI is a separate protocol for offloaded operations (clone, zero, etc.), completely unrelated to capacity management.
• D is wrong for the same first reason as C - you cannot push a capacity change from vSphere to PowerStore; the flow is always array-first, then refresh in vCenter.

Memory tip: Think "Array first, vSphere refresh" - for vVols, the storage array (PowerStore) owns the capacity, so changes always start there; vSphere only needs a refresh, never a service restart, to see the updated size.

No community discussion yet for this question.