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.

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.

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.

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.