An administrator needs to investigate a database server deployment failure, but the failed database server...

Failed NDB provisioning workflows normally perform a rollback that removes resources created during the unsuccessful operation, including the database server VM. For troubleshooting, the administrator can enable the global skip_rollback_global setting so that NDB does not execute this cleanup path. The failed VM is then preserved for inspection of its operating-system state, logs, network configuration, and database installation artifacts. Nutanix Support states that automatic deletion occurs only when delete_vm_on_failure is true and skip_rollback_global is false; other combinations preserve the VM and require manual cleanup afterward. Because the question specifically asks which global rollback option must be enabled, skip_rollback_global is the correct selection. It should be returned to its normal value after troubleshooting to avoid abandoned resources. Nutanix KB 14629