NCP-BC-7.5 Sample Questions Answers

Nutanix Disaster Recovery provides multisite replication capabilities, allowing a single cluster to protect workloads across multiple locations. However, there are specific architectural constraints regarding the type of replication schedules that can coexist within a single Protection Policy.

The primary limitation in this architect ' s design is that a single Nutanix Protection Policy supports only one synchronous replication schedule. While you can configure a policy to replicate to multiple sites using Asynchronous or NearSync schedules, you cannot natively instruct the system to perform a synchronous " 3-way " write where a single VM mirrors every I/O to two different physical destination clusters simultaneously. This is due to the extreme latency and metadata synchronization overhead that would be required to maintain zero-RPO consistency across three sites for every single write operation. Prism Central does allow pairing with more than one AZ (negating Option B), and synchronous replication is fully supported in Protection Policies (negating Option D). Therefore, to achieve the desired level of protection, the architect would need to use a combination of one synchronous schedule and additional asynchronous schedules to the second AZ, rather than attempting two simultaneous synchronous links within one policy.

The " Test Failover " feature in Nutanix Disaster Recovery is a critical tool for ensuring that a BCDR plan is actually functional before a real disaster occurs. The primary goal of a test failover is to validate the entire recovery orchestration—including power-on sequences, script execution, and network mappings—in a completely non-disruptive manner.

During a test failover, the virtual machines are recovered at the destination site using the most recent snapshots, but they are typically connected to an " Isolated " or " Test " network. This allows the administrator to log into the recovered VMs and verify that the application starts correctly without causing any IP address conflicts or interference with the live production systems at the primary site. Unlike a " Planned Failover " or " Unplanned Failover, " a test failover does not move the production workload (negating Option B) and does not stop ongoing replication (negating Option D). It is purely a validation task designed to identify gaps in the Recovery Plan, such as missing dependencies or incorrect network assignments, thereby providing confidence that the organization ' s RTO and RPO goals can be met during a real emergency.

Storage consumption in a BCDR environment is directly governed by two factors: the frequency of recovery points (RPO) and the length of time those points are kept (Retention). When a third-party backup solution integrates with Nutanix Protection Policies, it often takes over the management of the snapshot lifecycle.

If storage utilization is increasing unexpectedly at both sites, the most likely cause is that recovery points are not being expired or purged at the expected rate. The administrator should first review the retention settings within the backup solution. If the retention period is set too long, or if the backup software is failing to send the " delete " command to Prism after its local catalog is updated, snapshots will accumulate on both the primary and recovery Nutanix clusters, leading to a steady growth in storage consumption. Other factors like network segmentation (Option C) or encryption (Option B) affect traffic paths and security but do not directly influence the quantity of data stored on the disks. Recovery validation (Option A) might use temporary storage but should not cause a continuous, long-term increase. Therefore, aligning the retention policy of the backup software with the available cluster capacity is the primary troubleshooting step.

Nutanix allows for the encryption of replication traffic " on the wire " using IPSec tunnels between clusters. When an administrator enables network segmentation for Disaster Recovery, the replication traffic is moved from the default management network to a new, dedicated subnet and set of virtual interfaces.

Because the native replication encryption relies on IPSec gateways to secure the communication, the underlying VPN configuration must be aware of the network paths it is protecting. If the traffic is now originating from a new segmented subnet, the IPSec VPN gateway configuration at both the primary and recovery sites must be updated to include these new subnet ranges. If this step is missed, the encrypted tunnel will not recognize the segmented traffic as valid for the VPN, causing replication to fail even if the physical network is reachable. Regenerating KMS tokens (Option C) relates to data-at-rest encryption on physical drives, not traffic-in-transit. Restarting services (Option D) might be part of the general segmentation workflow, but the specific requirement for " encrypted replication " stability in this context is the alignment of the IPSec VPN policy with the new segmented network topology.

Nutanix Metro Availability is a continuous availability solution that provides a zero Recovery Point Objective (RPO) and near-zero Recovery Time Objective (RTO) across two sites. For this configuration, there are two distinct latency requirements that administrators must manage. First, the Round Trip Time (RTT) latency between the two storage clusters participating in the synchronous replication must be less than 5ms to ensure application performance is not significantly degraded by the write-synchronization process. Second, the Witness VM, which acts as an external arbitrator to prevent " split-brain " scenarios during a site failure, has a more flexible latency requirement. The maximum RTT between the Witness VM and the managed Protection Domains (PDs) must be less than 200ms. This higher threshold allows the Witness to be placed in a separate geographical region or a third-party cloud availability zone (AZ), ensuring it remains independent of the failure domain affecting the primary and secondary sites. If the latency to the Witness exceeds 200ms, the cluster may be unable to quickly acquire the lock necessary to automate failover, potentially causing the Metro Availability configuration to fail during an actual disaster event.

Nutanix supports two main types of snapshots: crash-consistent and application-consistent. A crash-consistent snapshot is taken at the storage layer without any awareness of the guest OS state; it is equivalent to pulling the power plug on a server. An application-consistent snapshot is more complex because it requires the Nutanix cluster to " quiesce " the applications (such as SQL Server or Exchange) inside the guest OS, flushing pending writes to disk to ensure data integrity.

To perform this quiescence on Windows VMs, the Nutanix cluster must communicate with the Windows Volume Shadow Copy Service (VSS). This communication is handled exclusively by Nutanix Guest Tools (NGT). If NGT is not installed on the VM, or if the NGT agent is not running/communicating with the cluster, the system cannot trigger the VSS hardware provider. In this situation, any request for an " application-consistent " snapshot from a third-party backup solution will fail because the cluster lacks the necessary hooks into the guest OS. However, a " crash-consistent " snapshot will still succeed because it does not require any guest-level interaction. Therefore, when app-consistent backups fail but crash-consistent ones succeed, the most likely root cause is a missing or broken NGT installation on the affected virtual machines.

Transitioning from legacy Protection Domains (which are cluster-centric) to modern Prism Central-based Protection Policies (which are management-plane centric) is a common task during Nutanix environment upgrades. This migration involves a " handoff " where the responsibility for snapshots and replication shifts from the local Cerebro service on the cluster to the global orchestration provided by Prism Central.

The primary risk during this migration is the creation of a " protection gap. " If an administrator deletes the legacy snapshots immediately after assigning a new policy, and that new policy has not yet successfully completed its first replication cycle, the virtual machine is effectively unprotected. If a disaster occurs at that exact moment, there would be no valid recovery points at the destination site to restore from. Nutanix best practice dictates that legacy artifacts must be preserved until the new system is verified as operational. Once the first recovery point for the VM appears in the Prism Central " Recovery Points " tab, it confirms that the new Protection Policy has successfully captured the VM ' s state and replicated it to the recovery AZ. At this stage, the legacy snapshots in the Protection Domain become redundant and can be safely deleted to reclaim storage space without compromising the organization ' s ability to meet its Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

Prism Central (PC) acts as the centralized control plane for Nutanix Disaster Recovery, storing the critical metadata for Protection Policies and Recovery Plans. If the cluster hosting the Prism Central instance suffers a total failure, the " brain " of the DR orchestration is lost, and the administrator cannot trigger the Recovery Plans through the usual interface. To address this risk, Nutanix provides the " Prism Central Backup and Restore " feature, which replicates the PC metadata to a remote cluster managed by Prism Element (PE). In a disaster scenario affecting Cluster A, the first and most critical step is to recover the management plane. The administrator must log into Prism Element on the surviving cluster and use the native recovery workflow to restore the Prism Central instance from the most recent backup. Once the PC instance is restored and booted on the surviving cluster, it will once again have access to the Recovery Plans and Protection Policies. Only after the management plane is restored can the administrator then initiate the " Unplanned Failover " tasks to bring up the protected workloads. This process ensures that the RTO is kept low by restoring the automated orchestrator rather than manually re-creating policies and plans on a new instance (Option B).

The primary purpose of a Test Failover is to validate the recovery process in a non-disruptive manner. When a VM is recovered from a snapshot during a test, it retains its original configuration, including its IP address and hostname. If this test VM were to be powered on on the same network as the live production VM, it would immediately cause a duplicate IP address conflict and potentially disrupt production services or trigger security alerts.

To prevent this disruption, Nutanix Recovery Plans allow administrators to map the production network to a " Test Network " at the recovery site. This test network is typically an " Isolated " VLAN or overlay network that has no physical or logical route back to the production environment. By using an isolated network (Option A), the test VMs can boot up, run their internal services, and even communicate with other test VMs (if placed on the same isolated segment) without any risk of interfering with real users or databases. This allows the infrastructure team to verify that the " Recovered " state is functional while the " Primary " state continues to serve the business, fulfilling the core requirement of non-disruptive testing.

Nutanix 2-node clusters are often used in small remote office (ROBO) environments to provide high availability with a smaller hardware footprint. However, the reduced node count introduces specific limitations on advanced data protection features compared to standard 3-node or larger clusters.

One of the key limitations of a 2-node cluster is the support for high-frequency replication. Technologies like NearSync (which provides RPOs from 1 to 15 minutes) and Synchronous replication (0 RPO) require a minimum of three nodes to manage the necessary metadata overhead, storage consistency, and lightweight snapshot (LWS) engine requirements. In a 2-node cluster, the system is restricted to using standard Asynchronous replication. The minimum RPO supported for standard Asynchronous replication in these small cluster configurations is typically 1 hour (60 minutes). An administrator attempting to set a more aggressive RPO will find that the system does not support the necessary lightweight snapshot infrastructure. Therefore, while a 2-node cluster provides excellent local availability, its off-site disaster recovery capability is limited to a 1-hour RPO, which should be considered during the initial architectural design and risk assessment phase for critical workloads.

In a Business Continuity strategy, " downtime " can be categorized as either unexpected (disaster) or controlled (maintenance). When an administrator knows that a disruption is coming, such as scheduled network maintenance on a primary cluster, they should utilize the " Planned Failover " mechanism within the Nutanix Recovery Plan.

A Planned Failover is a graceful, orchestrated migration. It first shuts down the virtual machines at the primary site to ensure all data is flushed and no new writes occur. It then performs a final synchronization to the recovery site to ensure zero data loss (Zero RPO), and finally powers the VMs on at the destination site according to the plan ' s sequence. This differs significantly from an " Unplanned Failover " (Option A), which assumes the primary site is already offline and may result in minor data loss depending on the last successful replication. A " Test Failover " (Option D) merely validates the process in an isolated environment and does not move the actual production workload. By executing a Planned Failover before the maintenance begins, the administrator ensures that the services are safely running on the target cluster, maintaining application availability and meeting the objective of zero downtime during the maintenance window.

Failing over to Nutanix Cloud Clusters (NC2) on AWS involves moving workloads from a local, on-premises networking environment into a cloud-native Virtual Private Cloud (VPC). While Nutanix Flow Virtual Networking (FVN) allows the VMs to keep their internal IP addresses using overlay networks, external visibility requires integration with AWS networking components.

Standard internal IP addresses in an overlay network are not natively routable from the public internet or from the AWS VPC outside of the NC2 cluster. To bridge this gap, Nutanix uses " Floating IPs " . A Floating IP is an AWS Elastic IP that is mapped to the internal IP of the guest VM. When an external user attempts to reach the website, the traffic hits the AWS public-facing Floating IP, which is then translated and routed through the NC2 bare-metal nodes to the specific guest VM. This mapping can be automated as part of the Recovery Plan or configured manually post-failover. Without this configuration, the VMs will remain " isolated " from external traffic, even if the application is running perfectly and internal cluster connectivity is healthy. This demonstrates the importance of cloud-native networking knowledge when extending on-premises BCDR plans into public cloud environments like NC2.

Nutanix Asynchronous (Async) replication is a foundational data protection technology that allows for the periodic transfer of virtual machine snapshots from a primary cluster to a remote site. When using Async replication between two ESXi-based Nutanix clusters, the primary objective is data persistence rather than deep integration with the vSphere management hierarchy. Because Async replication operates at the storage level, it captures the virtual disk (vDisk) data and the VM ' s configuration files (.vmx) but does not natively synchronize the logical inventory metadata maintained by the vCenter Server, such as VM folders, resource pools, or specific vApp configurations.

When a failover is executed, the Nutanix cluster registers the VM to the remote ESXi host and vCenter. Since the inventory mapping details (original folder and resource pool) are not part of the standard Async replication payload, the vCenter Server treats the failing-over VM as a new registration and places it into the default root folder and the default cluster resource pool. To maintain consistent organizational structures during a disaster recovery event, administrators typically rely on Prism Central-based " Recovery Plans. " Recovery Plans offer advanced orchestration that allows for the manual definition of inventory mappings, ensuring that VMs are placed in the correct folders and resource pools upon recovery. Understanding this limitation of legacy Async replication is crucial for administrators designing BCDR solutions that require high levels of organizational consistency post-failover.

Nutanix storage is often accessed by external backup solutions (like Veeam, Commvault, or HYCU) using the iSCSI protocol. This allows the backup server to mount snapshots and read data directly from the storage tier. The error message " iscsiadm... discovery... timeout " specifically indicates that the backup server ' s iSCSI initiator is unable to communicate with the Nutanix Data Services IP or the Controller VMs (CVMs) over the network.

When a Nutanix cluster is expanded, it is essential that all networking and firewall configurations applied to the existing nodes are also applied to the new nodes. The iSCSI protocol relies on specific TCP ports: port 3260 is the standard port for iSCSI traffic, and port 3205 is often used for iSCSI discovery and metadata operations within Nutanix. If these ports are not open in the physical firewall or the host-based security rules for the newly added nodes, the backup server will be unable to discover the targets on those specific nodes, leading to the timeout errors . This highlights a common " Day 2 " operational trap: cluster expansion requires careful auditing of network security groups and firewall whitelists to ensure that external integrations—especially BCDR and backup services—continue to have uninterrupted access to the expanded storage fabric. Verifying and opening ports 3205 and 3260 for the new node IPs is the first step to resolving this timeout issue.

IP address management (IPAM) in Nutanix networks ensures that IP assignments are tracked to prevent conflicts. When a Recovery Plan is validated, the orchestrator checks if it can successfully assign the required IPs at the recovery site. The warning occurs when the system detects a potential conflict or cannot automatically " guarantee " the preservation of a static IP, often due to overlapping pools or the way IPAM is configured on the destination subnet.

To resolve this without changing the VM ' s assigned IP, the administrator should use " Custom VM IP Mapping " . This feature allows the administrator to override the default automatic assignment and explicitly state which IP the VM must receive at the recovery site. By manually defining this mapping, the administrator " claims " the IP within the Recovery Plan ' s logic, satisfying the validation check and ensuring that the VM boots with its correct identity during a failover. Disabling IPAM (Option A) is often not feasible in production environments, and adding a vNIC (Option B) complicates the VM ' s OS configuration. Custom IP mapping is the purpose-built administrative tool for resolving IP assignment ambiguity and ensuring predictable recovery in complex, IPAM-enabled networking environments.

In a Nutanix environment, Synchronous replication (including Metro Availability and Synchronous Protection Policies) relies on a specialized service known as Anduril to manage the real-time mirroring and state transitions of virtual machines. While standard asynchronous replication primarily uses ports 2009 (Stargate) for data transfer and 2020 (Cerebro) for metadata and replication management, synchronous replication introduces additional requirements for low-latency communication between the Anduril services on the source and destination clusters.

The error message " Failed to connect to remote Anduril " specifically indicates that the local cluster ' s management plane is unable to communicate with the remote cluster ' s synchronous replication manager. TCP port 2036 is the dedicated port for cross-cluster communication between Anduril services. This port is used to negotiate the " stretch " of the VM across sites, coordinate the initial sync, and maintain the health heartbeat required for high-availability failover decisions. If port 2036 is blocked by a physical or virtual firewall between the clusters, the " VmSyncRepEnable " request will time out or fail, preventing the VM from ever entering the " Sync " (Active-Active) state. Troubleshooting synchronous replication always begins with verifying that the 5ms latency requirement is met and that port 2036 is open alongside the standard ports 2009 and 2020 to ensure both data and control traffic can flow without interruption between availability zones.

Orchestrating the recovery of multi-tier applications requires more than just powering on virtual machines; it requires managing the dependencies between application layers. In a standard 3-tier architecture, the Middleware and Web tiers typically depend on the Database being fully operational and ready to accept connections before they can successfully initialize. If a Recovery Plan powers on all tiers too quickly or simultaneously, the " upstream " services will fail to find their database backend, leading to the application crashes described in the scenario.

The Nutanix Recovery Plan provides " execution stages " to handle this boot ordering. However, even if tiers are in separate stages, a VM reaching a " Power On " state in the hypervisor does not mean the application services (like SQL or Oracle) are fully booted and ready for traffic. To address this, the administrator should configure " optional inter-stage delays " . This setting allows the administrator to define a specific wait time (in seconds) between the completion of one stage (e.g., Database power-on) and the start of the next (e.g., Middleware power-on). This delay gives the database engine enough time to finish its internal checks, mount its databases, and open its network ports. By incorporating these surgical delays, the administrator ensures a reliable, automated recovery where each tier only attempts to start once its required dependencies are fully operational at the destination site.

When designing disaster recovery to a cloud environment (such as NC2 on AWS or Azure), organizations must choose a compute model that aligns with their Recovery Time Objective (RTO). The " Zero Compute " model is the most cost-efficient because it stores only the data (snapshots) in low-cost Object Storage (S3 or Blob) and does not maintain a running cluster. However, the RTO for Zero Compute is high because, in a disaster, the organization must first deploy a new Nutanix cluster, configure it, and then begin the process of hydrating data from the Object Storage.

In contrast, the " Pilot Light " model involves keeping a minimal, active Nutanix cluster (e.g., 3 nodes) running at the recovery site. While this carries a moderate ongoing cost, it significantly reduces the RTO. Because the cluster already exists, the management plane (Prism Central), the storage containers, and all metadata are already active. When a failover is triggered, the system only needs to power on the VMs or perform a small amount of data hydration. This allows the organization to meet aggressive RTO targets of under 15 minutes, which is generally impossible with the Zero Compute model. Pilot Light provides the " ready-to-go " infrastructure needed for mission-critical applications that cannot afford the multiple hours required to provision a fresh cluster from scratch during an emergency.

Migrating from legacy Protection Domain (PD) based management to the modern Prism Central (PC) based Protection Policies is a recommended best practice for scaling Nutanix Disaster Recovery. This migration involves moving VMs from a " Prism Element " centric management model to a centralized, category-based model in Prism Central.

To ensure that no data is lost during this transition, the most critical prerequisite is to verify that a successful, full replication (backup) of the Protection Domain has recently completed. This ensures that the recovery site already possesses a complete and consistent set of data for the VMs before they are unlinked from the old policy and attached to the new one. While adding VMs to a category (Option A) is a step in the process, it is not the first verification step required for data safety. If an administrator attempts to migrate while a replication is incomplete or failing, the transition to the new policy might leave the VMs unprotected for an extended period, or recovery points might be missing if a disaster occurs mid-migration. By completing a full backup of the PD first, the administrator creates a " safety net " of recovery points that can be used if the migration itself encounters issues. This ensures that the transition to modern DR is performed with minimal risk to the business ' s data protection objectives.

Nutanix offers several data recovery methods, but the objective of " least disruptive " and " most efficient " is specifically addressed by the Self-Service Restore (SSR) feature. SSR is powered by Nutanix Guest Tools (NGT), which must be installed on the virtual machine. This functionality allows a user or an administrator to mount a disk from a historical recovery point directly to the active, running virtual machine as a temporary drive.

Once the snapshot is mounted, the guest operating system treats it as a standard local disk, allowing the user to browse the folder structure and perform a surgical restore of only the specific files that were deleted or corrupted. This process avoids the significant overhead and downtime associated with rolling back the entire VM (Option B) or cloning the VM to a new entity (Option C), which would consume additional compute and storage resources. Option A refers to Nutanix Files (NAS) functionality, which is separate from the block-level VM snapshot recovery discussed here. By using SSR/NGT, the production environment remains online and undisturbed, and the recovery process is delegated to the level of individual files, providing the highest level of granularity and efficiency in typical day-to-day data loss scenarios.

Establishing disaster recovery between an on-premises data center and a Nutanix Cloud Availability Zone (AZ) requires a robust communication path that can traverse different network boundaries. Unlike local replication within a single site, cross-site replication—especially to a public cloud environment—relies on the ability of the clusters to identify and reach one another over an external network. Nutanix Disaster Recovery requires that both the on-premises cluster and the Nutanix Cloud AZ instance have external IP addresses configured for their respective Controller VMs (CVMs) and virtual interfaces.

These external IP addresses allow the Cerebro service at the source site to establish a secure handshake with the Cerebro service at the cloud site. Without these routable external IPs, the replication traffic is unable to find its destination, leading to the immediate failure of the configuration as observed in this scenario. While identical hypervisors (Option A) are often preferred for simplicity, Nutanix supports Cross-Hypervisor DR (CHDR). Furthermore, deduplication status (Option C) does not prevent the establishment of a replication link. Synchronous replication (Option D) is restricted by latency requirements and is not a fundamental prerequisite for basic connectivity to a cloud AZ. Therefore, verifying the presence of external, reachable IP addresses is the mandatory first step in troubleshooting cross-site connectivity issues between on-premises and cloud environments.

Nutanix Guest Tools (NGT) is a software bundle that must be installed on the guest virtual machine (VM) to enable advanced management and data protection features within the Nutanix ecosystem. For the specific functionality of Self-Service Restore (SSR), NGT provides the necessary communication drivers and the Nutanix SSR agent. This agent allows end-users or administrators to mount recovery point snapshots as local drives directly within the guest operating system. Without NGT, the cluster lacks the specialized hooks into the guest OS required to perform granular file-level recovery without restoring the entire VM. Furthermore, NGT facilitates the creation of application-consistent snapshots by interacting with the Windows Volume Shadow Copy Service (VSS), which is often a prerequisite for high-integrity backups of Tier-1 applications like SQL Server or Exchange. By installing NGT, the VM is granted the intelligence to browse and attach historical vDisks, effectively enabling the SSR workflow and reducing the operational burden on the infrastructure team for simple file recovery requests.

In a Nutanix environment, " Advertised Capacity " is a logical limit (a quota) that an administrator can set on a specific storage container. Even if the physical storage pool has terabytes of free space, if a container ' s advertised capacity is reached, the hypervisor and the Nutanix services will perceive the container as being 100% full.

In this troubleshooting scenario, the " nfs status 28 " error code is a standard indicator for " No space left on device " . Since the administrator confirmed the pool is healthy, the logical limit on the container is the only remaining bottleneck. Replication jobs will " hang " because the destination Stargate service cannot write the incoming data blocks to a container that reports zero free space. To resolve this, the administrator must either increase the advertised capacity value in Prism or remove the limit entirely to allow the container to consume the available physical space in the pool. This highlights a common configuration " trap " where logical quotas—intended for multi-tenant management—can inadvertently block critical BCDR processes like replication if not monitored or sized correctly according to the protected VM growth.

Nutanix integration with third-party backup vendors like Commvault often relies on the Nutanix Guest Tools (NGT) to facilitate advanced backup features. NGT provides the necessary communication bridge between the guest VM ' s internal state and the Nutanix AOS storage layer. The " Virtual Machine not found " error in a Commvault context, despite the VM being visible in Prism, often indicates a breakdown in metadata communication or a mismatch in the guest agent ' s version .

If NGT is outdated or its internal " Nutanix Guest Agent " (NGA) service is failing, the backup software may be unable to retrieve the correct VM UUID or state information required to initiate an application-consistent snapshot. Upgrading NGT to the latest version ensures that the guest VM has the most current VSS hardware providers and metadata handlers, which are required for modern backup orchestration. Furthermore, NGT upgrades often resolve internal registration issues where the cluster fails to recognize the VM ' s active state due to legacy driver conflicts. By ensuring the NGT version is current and the NGA service is healthy, the administrator establishes a reliable communication path, allowing Commvault to correctly identify and process the VM for backup operations. This highlights the importance of maintaining NGT as part of regular cluster maintenance to ensure consistent BCDR functionality.

An In-place Restore (Revert) is the fastest way to roll back a VM because it overwrites the current vDisks with the data from the snapshot. However, this operation has strict requirements regarding the consistency of the VM ' s hardware configuration. The most common technical blocker for an in-place revert is a change in the disk topology between the time the snapshot was taken and the time of the restore.

If the administrator added a new 50GB data disk (Option D) after taking the snapshot, the VM ' s current configuration now includes a vDisk that does not exist in the snapshot ' s metadata. Nutanix AOS cannot " revert " a disk that has no point-in-time reference in the recovery point. In this situation, the " In-place Restore " button is typically disabled or will throw an error, forcing the administrator to use the " Clone " (Out-of-place) option. Cloning creates a new VM based exactly on the snapshot ' s metadata, effectively ignoring the newly added disk. While changing memory (Option B) or NGT versions (Option A) might affect performance or guest features, they do not usually prevent the storage-level revert operation. Being forced into a " Clone " restore increases the RTO slightly, as the administrator must then delete the corrupted VM and ensure the new clone has the correct network settings.

Modern Nutanix Disaster Recovery utilizes Prism Central-based Protection Policies and Recovery Plans, which offer more advanced orchestration and automation than legacy Prism Element-based Protection Domains. When an organization decides to upgrade its DR management, a careful migration path must be followed to ensure that VMs do not lose protection during the transition.

The first and most critical step is to migrate the virtual machines from the legacy Protection Domain to a new PC-based Protection Policy. This process involves adding the VMs to the correct Categories in Prism Central, which then associates them with the new policy. Once the VMs are " claimed " by the Protection Policy, the system will begin managing their snapshots and replication schedules according to the new logic. Only after the VMs are successfully protected under the new system is it safe to " unprotect " them and remove the legacy Protection Domains (and their associated snapshots) to reclaim storage. Attempting to delete snapshots first (Option A) or perform a failover (Option D) before the management handoff is complete could leave the business without a valid recovery point if an outage occurs during the migration window.

Self-Service Restore (SSR) is a Nutanix guest-level feature that empowers users to mount snapshots as local drives to recover individual files without administrative intervention. For SSR to function, the underlying data protection mechanism must support the specific metadata and disk-attachment hooks required by Nutanix Guest Tools (NGT). Asynchronous (Async) replication schedules are a primary supported technology for SSR because they create standard, persistent recovery points that are easily indexed by the SSR agent within the guest OS. While the question asks to " Choose two, " it is important to note that Nutanix also generally supports SSR for Synchronous replication (Option C), as both methods produce the point-in-time vDisk snapshots necessary for the mounting process.

Conversely, certain high-frequency technologies like NearSync (at very low RPOs) or complex storage entities like Volume Groups (VGs) have historically faced limitations with the SSR mounting workflow due to the way metadata is handled or how disks are presented to the hypervisor. In a production environment, an administrator must ensure that NGT is fully functional on the VM and that the VM is part of a compatible Protection Policy to enable the SSR " snapshot-to-drive " mapping. This capability is essential for balancing operational efficiency with user-led data recovery, as it offloads simple " deleted file " requests from the infrastructure team while leveraging the existing BCDR snapshot architecture.

Network segmentation in a Nutanix cluster allows for the physical or logical isolation of different types of traffic (management, storage, and backplane). When applied to Disaster Recovery, it allows an administrator to dedicate a specific network interface (typically ntnx0) and a dedicated subnet for replication traffic, ensuring it does not contend with VM or management traffic for bandwidth.

However, Disaster Recovery is a site-to-site operation that requires a symmetric network configuration. If an administrator enables segmentation on the primary cluster, the Cerebro service at that site will now attempt to originate and receive all replication traffic on the newly defined segmented IP addresses. If the recovery cluster is still in its original " brownfield " state without segmentation, it will be looking for traffic on its management IP addresses (on eth0). This creates a mismatch where the two sites are effectively " speaking different languages " or looking for each other on the wrong networks. Nutanix does not automatically propagate segmentation settings between clusters because each site may have different physical network topologies or VLAN requirements. Therefore, the administrator must manually enable and configure network segmentation on the recovery cluster to match the primary. Only when both sites have consistent segmented interfaces and the routing/firewall rules are updated to allow communication between these new subnets will the replication link be restored and functional.

Failback is a critical phase of the disaster recovery lifecycle where workloads are returned to their original primary site. When an " Unplanned Failover " is executed, the system assumes the primary site is gone or unmanaged. Once the primary site (AZ1) is restored, the administrator cannot simply " re-run " the failover in reverse without preparing the source site. The " Clean up of Entities " (Option C) is a mandatory step that must be performed on the original primary cluster after it returns to a healthy state. This process clears the stale VM registrations and metadata that existed prior to the outage, signaling to the Nutanix orchestrator that AZ1 is now ready to re-receive the workloads. Until this cleanup is completed, the Recovery Plan will not list the VMs as eligible for failback because it still detects the " ghost " of the VM at the destination. While reverse replication (Option B) is also necessary to prevent data loss during failback, the reason the VMs are entirely missing from the Recovery Plan interface during the initial failback attempt is the lack of entity cleanup. Performing this cleanup ensures a smooth transition back to primary production without metadata conflicts or registration errors.