According to the Nutanix Database Automation (NCP-DB) learning documents, an administrator can change the snapshot schedule for a given database by selecting the Time Machine, then under Action, select Update and define an appropriate schedule1. This is because the Time Machine in Nutanix Era allows you to specify the number of backups or snapshots the time machine should take, the time of day it takes those snapshots, and the day of the week it takes weekly or monthly backups1. These options help you build a complete schedule of time machine capture operations1. Even if the Time Machine is in a paused state, the administrator can still update the schedule1. Cloning the Time Machine or the database is not necessary for changing the snapshot schedule1.

NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.
NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.
References:
* Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment,
* Lesson 3.2: Nutanix Era Deployment, slide 11.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.2: Nutanix Era Alerts and Notifications, slides 5-7.

NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching
* Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software

* Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.
* Option B: Under the Capacity widget on the Database Server VMS > List database summary page.
While this might provide information about the capacity, it does not specifically provide the size of a Source Database.
* Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.
* Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.