C. Identify appropriate POC hardware:

It is essential to identify and confirm the hardware that will be used for the Proof of Concept (POC) to ensure that the resources match the requirements of the workloads being tested. This includes selecting Nutanix and HPE SimpliVity hardware that can be compared under similar conditions.

D. A test plan with agreed upon success criteria:

Developing a detailed test plan with agreed-upon success criteria ensures that both the prospect and the SE have a clear understanding of the goals and objectives of the POC. This includes defining performance metrics, features to be evaluated, and acceptable thresholds for success.

A clear test plan helps in systematically evaluating the capabilities of Nutanix versus HPE SimpliVity, ensuring that the evaluation is fair and comprehensive.

To determine the best configuration, we need to calculate the required storage, including the additional 20% growth and the capacity to re-protect in the event of a node failure:

Initial Storage Requirement:

Usable storage required: 15 TiB

Additional storage for 20% growth: 15×0.2=3 TiB15 \times 0.2 = 3 \text{ TiB}15×0.2=3 TiB

Total storage required: 15+3=18 TiB15 + 3 = 18 \text{ TiB}15+3=18 TiB

Storage with Re-protection:

To ensure data protection and availability, Nutanix typically uses a replication factor (RF) of 2, meaning each piece of data is stored twice.

Therefore, the total raw storage needed: 18 TiB×2=36 TiB18 \text{ TiB} \times 2 = 36 \text{ TiB}18 TiB×2=36 TiB

Given these calculations, we should look for a configuration that provides at least 36 TiB of raw storage. Based on typical Nutanix node configurations, Option D provides the best balance of cost and capacity, ensuring that the requirement for 36 TiB of raw storage is met.

Scenario Analysis :

The customer does not have access to vCenter or ESXi hosts on ACME Public Cloud.

ACME replicates copies of virtual disks to external storage.

Migration Feasibility :

Without access to vCenter or ESXi, tools like Xtract for VMs cannot directly access and migrate the VMs.

Nutanix Community Edition would not be feasible as it cannot replicate VMs directly without vCenter access.

Calm is used for automation and orchestration but not for direct VM migration from unsupported platforms.

Best Method :

Using the replicated VM copies on external storage provides a direct and viable migration path.

Import the VMs from external storage to the local Nutanix cluster, ensuring a smooth transition.

References :

Nutanix documentation on VM migration strategies.

Best practices for migrating VMs from external storage to Nutanix clusters.

C. N+1:

In the exhibit, the Failover option selected is "Standard (N+1)." This indicates that the configuration is set up for N+1 resiliency.

N+1 resiliency means that the system can tolerate the failure of one node without affecting the availability of the applications running on the cluster.

This is a standard level of resiliency where one additional node is available to take over in case of a failure, ensuring continuous availability.

References:

Nutanix documentation and the Nutanix Bible explain the different levels of resiliency, including N+1, and how they ensure data and application availability in case of node failures.

Understanding Customer Requirements :

The customer needs to run z/Virtual Machine (z/VM) for mission-critical workloads.

Nutanix Support :

z/OS and z/VM Support : Nutanix currently does not support IBM mainframe environments, including z/OS and z/VM.

C. ABS (Acropolis Block Services):

Acropolis Block Services (ABS) enables Nutanix storage to be used by external servers, providing the performance and benefits of Nutanix’s distributed storage fabric while allowing the customer to continue using their existing investment in Oracle servers.

ABS allows the integration of all-flash storage with the existing Oracle environment, addressing the prospect's preference for all-flash arrays while leveraging Nutanix’s advanced storage capabilities.

References:

Nutanix documentation on ABS describes its features and benefits, particularly its ability to integrate Nutanix storage with external servers and support high-performance applications like Oracle databases.

The Curator service in a Nutanix cluster is responsible for distributing storage optimization tasks. This includes managing and distributing tasks such as disk balancing, proactive scrubbing, compression, deduplication, and erasure coding.

Task Distribution : Curator runs on every node and is controlled by an elected Curator Leader who is responsible for task and job delegation.

Scan Types : Curator performs full scans every six hours and partial scans every hour to ensure optimal storage performance and resource utilization.

Optimization Activities : The service ensures efficient data placement and storage utilization across the cluster.

References :

Nutanix Bible: Provides an in-depth explanation of Curator and its role in the cluster​​.

Nutanix Documentation: Further details on the operations and management of Curator tasks.