In the event of failed CVM, what happens to the physically attached storage for the node and the VMs running on it?
In the event of failed CVM, what happens to the physically attached storage for the node and the VMs running on it?
In the event of a failed CVM, the drives for that node become inaccessible, but the VMs continue to run by accessing their data from replicated copies on other nodes within the cluster. This data redundancy is maintained through Nutanix's storage architecture which ensures data availability through replication, allowing VMs to continue functioning without rebooting.
D https://www.nutanix.com/blog/nutanix-controller-failure-will-users-notice
I would go on D option. NDFS uses replication factor (RF) and checksum to ensure data redundancy and availability in the case of a node or disk failure or corruption. In the case of a node or disk failure the data is then re-replicated among all nodes in the cluster to maintain the RF; this is called re-protection. Re-protection might happen after a CVM is down.
B, Data path redundancy?
I think it's B
B iis correct
When a local CVM can't provide data, remote CVMs supply the data from the RF2 remote copy of data extents, until the local one is back online. https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_0:arc-controller-vm-failure-c.html
B seems most likely. This article seems to indicate the disk would be unavailable and VMs would access the replicated data on other nodes https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_1:arc-node-failure-c.html
B is correct!
A. CVMs reboot during AOS upgrade, do your VM's reboot too? No! It's the whole point of virtualization/HCI. Answer A is wrong. B. This is correct! Current exam is for AOS 5.20. When a local CVM can't provide data, remote CVMs supply the data from the RF2 remote copy of data extents, until the local one is back online. https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_0:arc-controller-vm-failure-c.html Maybe this was different for older versions of AOS, but if your studying for the current one, then you need to prepare for questions referring to the current version! C. Remote CVMs provide the data over the network see link above, the hypervisor isn't aware of this! Also, VMs don't reboot. Why would you invest in expensive kit, if VMs were going to reboot on hardware failure?? D. Remote CVMs provide the data over the network -see link above, the hypervisor isn't aware of this!
It should be B. https://www.nutanix.com/blog/nutanix-controller-failure-will-users-notice "Although the primary copy of the guest VM data will be unavailable because it is stored on disks mapped to the failed CVM, the replicas of that data are still accessible"
Answer should be D. As per Nutanix Bible, page 76, In the event of a CVM “failure” the I/O which was previously being served from the down CVM, will be forwarded to other CVMs throughout the cluster. ESXi and Hyper-V handle this via a process called CVM Autopathing, which leverages HA.py (like “happy”), where it will modify the routes to forward traffic going to the internal address (192.168.5.2) to the external IP of other CVMs throughout the cluster. This enables the datastore to remain intact, just the CVM responsible for serving the I/Os is remote.
B, for sure
Ans. C once the CVM is unaccessible, nutanix will perform HA, VM will reboot.
D, other CVM from other host takes the control.
The correct answer is D. Only the cvm is failing, not the host. The other CVMs in the cluster always have access to the drives.