NCP-BC practice question 3 of 25

An administrator configures disaster recovery between an on-premises AZ and a Nutanix Cloud AZ. The deployment follows the documented workflow, and…

Full set: 109 questions

An administrator configures disaster recovery between an on-premises AZ and a Nutanix Cloud AZ. The deployment follows the documented workflow, and no configuration errors are reported during setup. After enabling DR and assigning protection policies to several VMs with volume groups, the administrator initiates failover and notices the VMs do not have their volume groups attached. To troubleshoot, the administrator performs the following verification steps: The clusters are successfully paired in Prism Central. Protection policies and replication schedules are configured correctly. Recovery plan validation completes successfully. Required firewall ports between sites are confirmed open. Management IP addresses are reachable in both directions. Despite this, the administrator observes the volume groups are still not attached. Which network-related prerequisite is most likely misconfigured?

Answer options
A:

A. Nearsync replication does not support volume groups.

B:

B. The clusters do not have a Data Services IP addresses configured.

Correct answer
C:

C. The recovery plan has not been validated.

D:

D. The hypervisor management interfaces are not on the same subnet.

Correct Answer:
B. B. The clusters do not have a Data Services IP addresses configured.
Explanation

Nutanix Volume Groups provide block storage to VMs and external clients using the iSCSI protocol. For the iSCSI service to function, a Data Services IP address must be configured on the cluster. This IP address serves as the discovery portal and data endpoint for iSCSI initiators. In a disaster recovery scenario, if the destination cluster lacks a configured Data Services IP, the iSCSI targets for the replicated volume groups cannot be brought online. Consequently, the VMs will failover, but the iSCSI initiators within them cannot connect to their VGs, leaving them unattached.

Why Incorrect

A. Nearsync replication does not support volume groups: This is incorrect. Nearsync, Asynchronous, and Synchronous replication all support the protection of Volume Groups.
C. The recovery plan has not been validated: The scenario explicitly states that the "Recovery plan validation completes successfully," ruling this out as the cause of the issue.
D. The hypervisor management interfaces are not on the same subnet: This is not a prerequisite for DR or Volume Group functionality. Clusters in different sites are expected to be on different subnets.

References

1. Nutanix Volumes Guide, Version 6.8, "Prerequisites and Limitations", Section "Cluster-Level Prerequisites". This section explicitly states, "Configure a Data Services IP address in the cluster."

2. Nutanix Data Protection and Recovery with Prism Element Guide, Version 6.8, "Protection of Volume Groups". This section outlines the requirements for protecting VGs, which implicitly relies on the underlying Volumes service being correctly configured with a Data Services IP on both source and target clusters.

Scroll to Top