What is the best practice when deploying an HPE OneView appliance?

Question

Options

• AEnable VMware Fault Tolerance if the appliance is deployed to a VMware hypervisor.
• Bdeploy the appliance in a hypervisor cluster that Is not managed by OneView.
• CUse thin-provisioning for the HPE OneView appliance to save storage capacity.
• DDeploy two HPE OneView appliances and configure them in HA mode.

• A
  7% (2)
• B
  85% (23)
• C
  4% (1)
• D
  4% (1)

Explanation

Deploying the HPE OneView appliance in a hypervisor cluster that OneView itself does not manage avoids a dangerous circular dependency - if OneView manages the very hosts it runs on, a failure could leave you unable to recover the appliance using the tool you need to fix the problem.

Why the distractors are wrong:

• A - VMware Fault Tolerance (FT) is not supported or recommended for OneView; it has strict VM constraints and is not the HA mechanism HPE prescribes.
• C - Thin provisioning is explicitly discouraged for OneView; HPE requires thick provisioning to guarantee the disk performance and capacity the appliance needs.
• D - OneView does support a native backup/restore model, but there is no traditional "HA pair" configuration between two OneView instances the way you'd configure, say, two load balancers.

Memory tip: Think "don't saw off the branch you're sitting on" - OneView can't safely manage the hosts it lives on, so keep it on a separate, unmanaged cluster.

No community discussion yet for this question.