QuestionQ92

Storage Network Design

Refer to the exhibit.

Question Image

A Cisco engineer is configuring a next-generation Cisco HyperFlex HX data platform with 2 x Cisco UCS 6248UP fabric interconnects, 8 x Cisco HX-Series HX240c-M4SX servers, plus 8 x Cisco UCS B200-M4 blade servers, a Cisco UCS 5108 blade chassis, and Cisco UCS 2204XP fabric extenders. The solution is configured with HX Release 4.5(2a) using VMware ESXi 7.0 U2. After migrating all customer VMs to the new solution platform, the engineer decides to create HX Native snapshots for all VMs. The engineer performs the operation and notices that some VMs do not create snapshots. What is the most probable reason the HX Native snapshots are not created?

  • A The servers have duplicate names.
  • B The source disk is thick provisioned.
  • C Virtual machines are in suspended state.
  • D The node has insufficient data storage space.
Explanation

HX Native Snapshot creation is not supported for virtual machines in a suspended state. Thick-provisioned disks can be snapshotted (the resulting snapshot is also thick), while the documented capacity prerequisite is that the storage cluster has sufficient available space and the datastore is accessible.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!