Helping Hand Questions for NCP-BC-7.5

Security hardening for BCDR is focused on protecting the integrity of recovery points against accidental deletion, administrative errors, or malicious intent such as ransomware. While infrastructure-level hardening like SSH keys (Option C) or host-level security (Option A) is important, they do not prevent a user with valid administrative credentials in Prism from deleting a snapshot. To address the specific requirement of ensuring only " authorized " and verified actions can modify or delete snapshots, the administrator should implement an " Approval Policy " .

An Approval Policy introduces a " four-eyes " principle for critical management tasks. When this policy is active, any attempt to delete or modify a recovery point does not execute immediately. Instead, it triggers a request in the Prism Central " Task " console and enters a " Pending Approval " state. A separate authorized user—an " Approver " —must then review the request and explicitly grant permission before the deletion can occur. This creates a vital procedural safeguard, ensuring that no single individual has the unilateral power to destroy the organization ' s backup data. By configuring this policy, the administrator hardens the DR environment against both internal threats and external actors who might gain access to a single set of admin credentials, providing a robust layer of defense for critical data assets.

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.

Modern Nutanix Disaster Recovery (Leap) relies on " Categories " to automate the inclusion of virtual machines into Protection Policies and Recovery Plans. When a Protection Policy is created, it is typically applied to a category (e.g., AppType:SQL) rather than individual VM names.

In this scenario, the newly deployed VMs were missed during a test failover despite other VMs on the same cluster recovering successfully. The most likely root cause is that the application team, working independently, failed to assign the required categories to the new VMs during the provisioning process. Because the VMs lacked the correct category tags, the Nutanix Protection Policy did not " see " them, and consequently, no recovery points were ever created for them. This is a common operational failure in environments where " infrastructure as code " or strict provisioning standards are not enforced. Recovery Plans (Option A) do not need manual re-synchronization for new VMs if the categories are correctly mapped. While an initial sync is required (Option D), it would typically show a task or progress rather than just leaving the VMs " missing " from the entire protection summary. Therefore, verifying category assignment is the primary troubleshooting step.

Validation is a core pillar of a robust Business Continuity and Disaster Recovery (BCDR) strategy. Nutanix provides built-in orchestration through Recovery Plans, which automate the failover process of virtual machines between sites. When a " Test Failover " is executed, the system performs all the necessary steps, such as booting VMs in an isolated network, applying network mappings, and executing any custom scripts. To provide visibility into this process, Nutanix generates an automated execution report upon completion of any Recovery Plan task. This report provides a detailed chronological breakdown of every action performed by the orchestrator, including the exact start and end times for each stage (e.g., " Replication Check, " " Power On, " " IP Assignment " ). This built-in reporting is superior to manual event log filtering because it aggregates all related activities into a single, digestible summary that specifically tracks the performance of the DR plan. For leadership and compliance teams, these execution reports serve as documented proof that the RTO (Recovery Time Objective) is achievable and that every orchestrated step was validated during the test window.