Practice Free NCP-BC-7.5 Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 Exam Questions Answers With Explanation

This question evaluates the administrator ' s ability to map business RPO (Recovery Point Objective) requirements to the appropriate Nutanix technology. A requirement for " maximum 15 minutes of data loss " means the system must replicate data at least every 15 minutes. Nutanix offers two primary ways to achieve this: traditional Asynchronous replication and Nearsync replication. While Async (Option D) can technically be configured for a 15-minute interval, it relies on standard, full snapshots which can be heavy and resource-intensive, potentially leading to performance lag if the data churn is high. Nearsync Replication (Option B) is specifically designed for these low-RPO scenarios (from 20 seconds up to 15 minutes) by using " Lightweight Snapshots " (LWS). LWS minimize the storage and I/O overhead compared to traditional snapshots, making Nearsync the more reliable and robust choice for Tier-1 applications. Furthermore, Nearsync is built to handle the constant, high-frequency data transfers required to maintain a strict 15-minute window without impacting application performance. Therefore, Nearsync with a 15-minute RPO is the " best " configuration because it is the purpose-built solution for the stated performance and data protection goals.

Replication in a Nutanix environment always begins with an " initial seed " . This first replication task is a full, 1-to-1 copy of all the data blocks currently occupied by the virtual machines on the source cluster. Unlike subsequent incremental snapshots—which only transfer the changed blocks—the initial seed requires sufficient physical or logical space at the destination to hold the entire data set of the protected VMs.

In this scenario, the administrator attempted to protect 4TB of virtual machine data but restricted the destination container ' s capacity to a mere 200GB. Because the destination container reports only 200GB of available space, the replication job will immediately stall or fail to progress as soon as the incoming data stream exceeds that limit. Nutanix replication requires a " landing zone " that can accommodate the full size of the initial snapshot before it can begin the process of data reduction (like compression or deduplication) at the remote site. To fix this, the administrator must increase the advertised capacity of the VMData container on Cluster B to at least 4TB (plus overhead for future growth and snapshots) to allow the initial full seed to complete successfully, thereby establishing the baseline for the BCDR protection schedule.

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.

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).

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.

Nutanix Metro Availability is a continuous availability solution designed to survive a site failure with zero data loss (Zero RPO). Because it operates on a synchronous replication model, every write performed by a virtual machine must be acknowledged by both the local and the remote clusters before the write is confirmed to the application. This process introduces a " latency penalty " equal to the network Round Trip Time (RTT) between the sites.

To maintain acceptable application performance and ensure cluster stability, Nutanix enforces a strict latency limit of 5 ms RTT between the primary and secondary clusters. If the latency exceeds this 5 ms threshold, the time spent waiting for remote acknowledgments would cause severe performance degradation for high-I/O workloads, such as the SQL or Oracle databases common in financial institutions. Furthermore, high latency increases the risk of the synchronous link being " broken " during periods of high data churn. While the Witness VM (used for tie-breaking) can tolerate much higher latency (up to 200 ms), the data-path link must remain under 5 ms to satisfy the technical requirements of the Metro Availability feature and the performance expectations of Tier-1 business-critical applications.

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.

Replication between Nutanix clusters involves the transfer of both actual data blocks and the metadata required to manage the consistency and scheduling of those snapshots. Two specific services running on the Controller VMs (CVMs) are responsible for these tasks: Stargate and Cerebro.

Port TCP 2009 is used by the Stargate service. Stargate is the primary I/O manager for the Nutanix cluster, and in a BCDR context, it handles the " Snapshot-on-wire " data transfer. This is the port where the actual bits of the virtual disks are sent from the source cluster to the destination cluster. Port TCP 2020 is used by the Cerebro service. Cerebro is the replication engine that handles protection domain orchestration, snapshot scheduling, and cross-site handshake operations. Without port 2020, the clusters cannot synchronize their schedules or confirm that a recovery point has been successfully stored at the remote site. While other ports like 9440 (Prism management) and 22 (SSH) are used for administrative tasks, ports 2009 and 2020 are the mandatory " data path " and " control path " ports required for the continuous and successful replication of workloads between availability zones.

In the Nutanix Disaster Recovery orchestration workflow, Network Mapping is a critical step that tells the system which production VLAN at the primary site corresponds to which VLAN at the recovery site. This ensures that when a VM is recovered, its virtual NIC (vNIC) is " plugged in " to a functional and valid network at the new location.

If an administrator leaves the Network Mapping section blank, the Nutanix orchestrator has no information about where to connect the VM ' s network interface. In this scenario, the priority of the system is to ensure the VM can boot and start its services without causing a " network storm " or security risk. If the system were to simply attach the VM to a random or default network, it could cause IP address conflicts or expose the VM to the wrong security zone. Therefore, the built-in behavior for a failover without a valid mapping is to recover the VM with all its network adapters in a " disconnected " state. The vNIC still exists on the VM, but the " connected " checkbox in the hypervisor is unchecked. This explains why the application owners report that the VMs are " isolated. " To fix this, the administrator must either update the Recovery Plan with the correct mappings and re-run the task or manually connect each VM ' s vNIC to the correct local VLAN in the recovery site ' s Prism interface.

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.

Hardening a Nutanix cluster for Business Continuity involves implementing security controls that protect recovery data from unauthorized destruction. In many modern cyberattacks, specifically ransomware, the goal is not just to encrypt production data but also to delete the snapshots and backups that would allow for recovery. To satisfy the requirement that only authorized modifications occur, the administrator must move beyond simple Role-Based Access Control (RBAC) and implement an " Approval Policy " .

The Approval Policy feature in Prism Central forces a secondary layer of validation for sensitive operations like snapshot deletion. When a user tries to delete a recovery point, the Nutanix orchestration engine captures the request and holds it in a " Pending " state. The request must be reviewed and approved by a designated person with approval authority. This ensures that even if an administrator ' s account is compromised, the attacker cannot immediately wipe out the snapshots needed to restore the environment. This " multi-person control " is a recognized security best practice for protecting mission-critical data. While cluster lockdown (Option C) prevents unauthorized SSH access, it does not manage the logical management of data through the Prism UI. An Approval Policy provides the specific " modification and deletion " control requested, ensuring that the cluster ' s recovery points remain a reliable " source of truth " following a security incident or administrative error.

Security and compliance are critical components of a Business Continuity strategy, particularly regarding the integrity of backups and snapshots. To prevent accidental or malicious deletion of critical recovery points, Nutanix Prism Central allows administrators to configure " Approval Policies " . These policies enforce a " four-eyes " principle where certain high-risk actions require validation by a second authorized user.

When an Approval Policy is active for DR snapshots, and a user attempts a deletion, the system does not execute the command immediately. Instead, the Nutanix orchestration engine captures the request and creates a " Pending Approval " task. The user who initiated the request will see the status update in the Task console, and an notification is sent to the designated " Approvers " . The snapshot remains fully protected and available for recovery until an authorized approver reviews and explicitly grants permission for the deletion. This mechanism provides a vital layer of defense against ransomware or administrative errors that could otherwise lead to the loss of a known-good recovery state. By integrating approval workflows into the storage management layer, Nutanix ensures that data destruction is a deliberate and verified process, meeting the strict control requirements of modern enterprises.

Nutanix Disaster Recovery (formerly known as Leap) utilizes Prism Central-based " Categories " to group virtual machines for protection. These categories are used within Protection Policies to determine replication schedules and within Recovery Plans to determine power-on sequences and network mappings. A common operational concern is the need to manually replicate these category definitions across different availability zones (AZs).

To reduce this operational overhead, Nutanix has implemented an automatic synchronization mechanism. When an administrator creates a Recovery Plan in Prism Central and specifies certain categories for failover, the system automatically synchronizes the definition and metadata of those categories to the paired recovery AZ. This ensures that if the primary Prism Central instance becomes unavailable, the recovery site already possesses the necessary grouping logic to identify and recover the correct virtual machines . This " policy-driven " approach ensures consistency across sites and eliminates the risk of human error associated with manual configuration (Option B). By automating the lifecycle of categories between paired sites, Nutanix ensures that the disaster recovery environment is always aligned with the production environment, allowing for seamless failover and failback operations without the need for repetitive administrative tasks.

In a complex BCDR environment, replication failures that affect only a specific subset of virtual machines—while others on the same cluster succeed—usually point to a configuration mismatch rather than a general network or storage issue. Since the ports (2009 and 2020) are confirmed open and storage is available, the transport layer is functional. The fact that Linux VMs are succeeding while Windows (Marketing) VMs are failing suggests that the two groups may be mapped to different destination storage containers. In Nutanix replication, if a container mapping is explicitly set for one set of entities (the Linux VMs) but not for another (the Marketing VMs), the second group might be defaulting to a destination container that is either missing, misconfigured, or has restricted permissions. This specific scenario implies that the successful Linux VMs are benefiting from a correctly configured container mapping on the remote site, whereas the Marketing VMs are likely attempting to replicate to a location where mapping is invalid or non-existent. Troubleshooting this requires an administrator to verify the Prism Central container mapping settings to ensure that the storage targets for all protected categories are reachable and correctly associated with the destination storage pool.

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.

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.

Migrating from legacy Protection Domains to modern Prism Central Protection Policies involves transitioning the management of virtual machine snapshots. During this process, the historical snapshots created by the Protection Domain are often intended to be " claimed " or utilized by the new PC-based system as valid recovery points.

Snapshots are point-in-time references to data on the storage tier. If a snapshot is deleted from the cluster before the migration to Protection Policies is finalized, the underlying data blocks associated with that specific point in time may be reclaimed by the system ' s garbage collection process. Consequently, the recovery points that were associated with that deleted snapshot will no longer be available for use within the new deployment. The system cannot " automatically recreate " (Option A) a deleted snapshot because the exact historical state of the data is lost once the snapshot is purged. The migration itself typically continues for the remaining valid data, but the loss of historical recovery points could impact the business ' s ability to restore to specific past dates. This highlights the importance of data retention awareness during management-plane migrations.

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.

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 Disaster Recovery environment using Protection Policies (Prism Central-based), the system needs to know which storage container at the recovery site should receive the replicated data from the primary site. This is known as " Container Mapping. " By default, Nutanix uses an " Automatic Container Mapping " feature to simplify administration.

The automatic mapping logic relies on matching names. If a VM is in a container named SalesA at Site A, the system will look for a container named SalesA at Site B to land the data. If the administrator manually created a container at the recovery site but named it SalesB (as in this scenario), the automatic mapping will fail because the names do not match. The system will instead attempt to find a container with the same name, and if it fails to find one, it may create a new one automatically or replication might fail. The fact that SalesB shows 0 bytes confirms that no data was ever sent to that specific container. To fix this, the administrator should either rename the destination container to match the source (SalesA) or manually configure a " Storage Container Mapping " in Prism Central that explicitly links the SalesA container on Cluster A to the SalesB container on Cluster B.

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.

Volume Groups (VGs) are used in Nutanix to provide block storage to virtual machines, often for high-performance applications like SQL Server. VGs can be attached to VMs in two ways: " In-guest " (using iSCSI initiators) or " Hypervisor-attached " (where the hypervisor handles the connection).

In a disaster recovery scenario managed by Recovery Plans, there is a technical distinction in how these attachments are handled. While Nutanix Disaster Recovery can replicate the data in the Volume Groups and recover the VM itself, VGs that are " hypervisor-attached " do not currently support automatic reattachment as part of the orchestration workflow in all AOS versions. When the failover completes, the VM powers on at the recovery site, but the VGs are not connected to the VM at the hypervisor level. This causes the application (SQL) to find its data disks missing, resulting in the database staying offline. To resolve this, the administrator must manually reattach the Volume Groups to the VM at the recovery site using the Prism interface or a script. This limitation highlights the need to verify specific application storage configurations during DR testing. For automated recovery of VGs, using " In-guest " iSCSI attachments is often preferred because the iSCSI initiator within the guest OS can re-establish the connection to the new cluster ' s Data Services IP once the network is active.

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.

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.

Cross-Cluster Live Migration (CCLM) is an advanced feature that allows a running VM to move between two clusters without downtime, provided they are linked by synchronous replication. However, CCLM has specific technical prerequisites and limitations regarding the VM ' s hardware configuration. One of the primary constraints in many Nutanix versions is the support for specific disk controllers.

In many CCLM implementations, the migration engine requires the VM to use modern VirtIO controllers for its disks to ensure that the memory-state transfer and storage-handoff can occur seamlessly across clusters. If MarketVM was configured with legacy SCSI controllers (or certain types of shared disks), the migration task might fail during the validation phase. While storage capacity (Option B) and bandwidth (Option C) are essential for general replication, they would typically prevent the " Synchronous " status from being achieved in the first place, rather than failing a CCLM task specifically. Memory overcommit (Option D) is generally handled by the hypervisor and would not inherently block the migration unless the destination host had zero available physical memory. Troubleshooting CCLM requires an administrator to audit the VM ' s virtual hardware against the supported Nutanix compatibility matrix to ensure all components are eligible for live cross-site movement.

Self-Service Restore (SSR) is a Nutanix feature that allows end-users to recover individual files by mounting a recovery point as a local drive within the guest VM. NearSync replication provides high-frequency protection with Recovery Point Objectives (RPOs) as low as 1 minute using Lightweight Snapshots (LWS). However, there is a technical distinction in how these high-frequency points are handled for end-user recovery.

In a NearSync configuration, the system generates dozens of LWS throughout an hour. While these are available for full VM disaster recovery, Nutanix limits the " granularity " available for Self-Service Restore to manage metadata overhead and guest agent performance. By default, SSR in a NearSync environment typically supports recovery point intervals of 1 hour. This means that while an administrator can restore the entire VM to a state from 5 minutes ago, an end-user using the SSR browser inside the VM will see recovery points at 1-hour increments (the " consolidated " points). This design balances the need for high-frequency disaster protection with the operational efficiency of file-level recovery. If a user needs a file from a point between the hourly intervals, an administrator may need to perform a full VM clone or an " Out-of-place " restore to provide access to those more granular lightweight recovery points.

When a primary Nutanix site suffers a catastrophic failure, the disaster recovery plan must be executed from the recovery (secondary) site . In a legacy Protection Domain-based environment, the secondary site is in a " passive " or " standby " mode, receiving snapshots but not actively running the workloads. The traditional method to failover is using the " Activate " command (Option A), which promotes the PD and registers the VMs. However, in certain specific failure scenarios or older software versions, the secondary cluster may require a service-level reset to recognize its new role as the active master for those specific workloads.

The Cerebro service is the core component responsible for managing Protection Domains and replication metadata. If the primary site is completely inaccessible and the secondary site ' s metadata state needs refreshing to initiate recovery, restarting the Cerebro service on the secondary cluster CVMs can force a re-evaluation of all local snapshots and protection domain states. This action triggers the recovery logic, allowing the administrator to then see and activate the recovery points. While " Activate " is the goal, the first technical step in a situation where the cluster management plane is unstable or the primary is gone is ensuring the data protection services are aware of the current state. This allows the VMs to be restored from the latest snapshots, fulfilling the Recovery Time Objective (RTO) despite the complete loss of the source infrastructure.