When a vCenter instance managing multiple clusters, including a Nutanix cluster hosting the NDB service, crashes and a new dedicated vCenter server is deployed, the administrator must update the vCenter settings within NDB to re-establish connectivity and management. The correct action is to navigate to the NDB Administration page, where cluster and vCenter configurations can be updated. This page allows the administrator to re-register the new vCenter instance, ensuring NDB can continue to manage the clusters and database VMs effectively. This approach avoids unnecessary reconfiguration wizards or waiting for automatic syncs.
* Option A (Click the Getting Started page and perform the configuration wizard) is incorrect because the Getting Started wizard is for initial setup, not post-crash vCenter updates.
* Option B (Update cluster settings from the NDB administration page) is correct as it provides the specific interface to modify vCenter settings after a crash.
* Option C (Open the maintenance page in NDB and configure the cluster settings) is incorrect because the maintenance page is for service operations, not vCenter reconfiguration.
* Option D (Wait 60 minutes and Prism Central will automatically sync NDB) is incorrect because Prism Central does not automatically sync vCenter settings in NDB; manual updates are required.
This ensures seamless integration with the new vCenter instance.
References
* Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Updating vCenter Settings
* Nutanix Support & Insights, Knowledge Base Article: "Reconfiguring vCenter in NDB After Failure"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 6: Administer an NDB Environment