Nutanix NCP-DB key terms

A control-plane product that provisions, clones, patches, backs up, and governs database engines such as PostgreSQL, MySQL, SQL Server, and Oracle across on-premises and cloud targets through a single management interface.

The service that runs on the NDB control plane and coordinates database operations, storing metadata, scheduling jobs, and driving registered database engines across managed clusters.

The virtual machine hosting the NDB control plane and Era services; it communicates with Prism Element and Prism Central and must be registered to the clusters it manages.

A guest VM created and managed by NDB that runs a supported database engine; it carries the database software, data disks, and NDB agents used for snapshots and lifecycle operations.

Software installed inside a database server VM that executes engine-specific tasks such as taking snapshots, applying patches, and reporting status back to the NDB control plane.

An NDB policy object attached to a database that defines snapshot and log capture schedules, retention, and the SLA used for restore and point-in-time recovery.

A point-in-time copy of a database VM's storage, typically created through Nutanix snapshots, that NDB uses as the basis for clones, backups, and recovery operations.

Rules that determine how many snapshots or backups NDB keeps and for how long, controlling storage consumption and the recovery window available to administrators.

Capture of database transaction logs by NDB on a schedule, enabling recovery to a precise moment between full snapshots rather than only to snapshot boundaries.

Restoring a database to a specific timestamp by combining a base snapshot with subsequent transaction logs, typically used to recover from logical errors such as accidental deletes.

A copy of a database created from a snapshot or backup, using storage-efficient Nutanix clones so new environments can be produced quickly with minimal capacity overhead.

A clone whose storage blocks are shared with the source until modified, so the clone consumes little additional capacity and can be created in seconds.

Replacing the contents of an existing clone with a newer snapshot of its source database, preserving the clone's identity, IP address, and configuration.

An NDB operation that copies database data from a source to a target, used to seed a clone or move data without recreating the target database from scratch.

A reusable NDB template that bundles database engine version, compute and storage sizing, network settings, and software profile choices used when creating new databases.

An NDB definition of the database engine binaries and version to install on a database server VM, referenced by provisioning profiles and patch operations.

An NDB object describing VLAN, subnet, gateway, DNS, and IP allocation settings applied to database server VMs during provisioning.

Applying an approved database engine software update to a managed database, typically preceded by a snapshot so the operation can be rolled back if it fails.

Moving a database to a major or minor engine version, such as a PostgreSQL major release, which may require additional steps beyond routine patching.

Reverting a database to its pre-operation state, usually by restoring the snapshot or backup taken before a patch or upgrade was applied.

Adding or removing compute or storage resources for a database server VM, such as increasing vCPU, memory, or data disk size, to match changing workload demand.

Recovering a database from an NDB snapshot, backup, or log stream, either in place over the original database or into a new database server VM.

A stored copy of database data created from snapshots or engine-native dumps, kept according to retention rules and usable for restore or clone operations.

In NDB, the service-level definition attached to a database that specifies snapshot and log schedules, retention, and the recovery objectives the platform enforces.

Role-based access control in NDB, where roles bundle permitted operations and are assigned to users or groups, restricting who can provision, patch, restore, or delete databases.

A named collection of NDB permissions, such as database administrator or read-only operator, that is assigned to users or groups to grant scoped capabilities.

An NDB rule that binds a role to a user or group and limits its scope to specific projects, clusters, or databases, enforcing least privilege.

An external identity source such as Active Directory or LDAP that NDB can integrate with so users authenticate with directory credentials and inherit group-based roles.

An NDB grouping construct that organizes databases and resources and scopes access control, allowing teams to work within boundaries without affecting other groups.

The step of registering NDB with Prism Central so the control plane can discover clusters, use categories, and integrate with Nutanix centralized management features.

The per-cluster Nutanix management service that NDB uses to create VMs, take storage snapshots, and manage the storage containers hosting database data.

Adding a Nutanix cluster to NDB so it can host database server VMs, with network, storage, and image configuration verified before provisioning.

A notification generated by NDB when a policy, job, capacity, or health condition crosses a threshold, delivered through email or integrated alert channels.

A periodic or on-demand assessment of NDB components and managed databases that reports issues such as agent connectivity, snapshot failures, or low storage.

A tracked NDB operation such as provisioning, patching, snapshotting, or restoring, with status, progress, and logs used for monitoring and troubleshooting.

Gathering NDB and database engine logs into a bundle for diagnosis, commonly requested by support when investigating failed jobs or unexpected behavior.

Software installed in database server VMs that enables snapshot consistency, self-service restore, and guest-level operations used by NDB workflows.

Making a database engine and its versions available to NDB by uploading engine binaries and creating software profiles used during provisioning and patching.