### Human: Can you tell about NCC Health Check: aged_third_party_backup_snapshot_check and  aged_entity_centric_third_party_backup_snapshot_check. ### Assistant: The NCC health checks aged_third_party_backup_snapshot_check and aged_entity_centric_third_party_backup_snapshot_check check the cluster for dangling third-party backup snapshots that may be present for a protection domain longer than intended/specified.. The NCC health checks aged_third_party_backup_snapshot_check and aged_entity_centric_third_party_backup_snapshot_check check the cluster for dangling third-party backup snapshots that may be present for a protection domain. If a third-party backup snapshot has existed in the system for longer than the specified period, this check will raise an alert. These backup snapshots are snapshots that are generated from third-party backups (Veeam, Commvault, Rubrik, HYCU, etc.).

Running the NCC Check

Run this check as part of the complete NCC health checks.

nutanix@cvm$ ncc health_checks run_all

Or run the check separately.

Third-Party backup snapshot check:

	nutanix@cvm$ ncc health_checks run_all
	Entity Centric Specific check:
	nutanix@cvm$ ncc health_checks run_all
	

You can also run the checks from the Prism web console Health page: select Actions > Run Checks. Select All checks and click Run.

This check is scheduled to run every day, by default.

Sample Output

For status: PASS

Third-Party backup snapshot check:

nutanix@cvm$ ncc health_checks run_all

Entity Centric Check:

nutanix@cvm$ ncc health_checks run_all

For status: FAIL

Third-Party backup snapshot check:

nutanix@cvm$ ncc health_checks run_all

Entity Centric Specific check:

nutanix@cvm$ ncc health_checks run_all

Starting AOS 5.15.3 and 5.18.1 and above, backup snapshots created without an expiration time are assigned a default 60 days expiration.From NCC 3.10.1 and higher on AOS version 5.15.3 and 5.18.1 and above, the check will only fail if the snapshots have an infinite expiration (ex 2086) and have exceeded the threshold set for the alert (default 7 days). Output messaging

Check ID110250DescriptionCheck for aged third-party backup snapshots.Causes of failureThird-party backup snapshots are present in the cluster longer than the configured threshold.ResolutionsContact Nutanix support.ImpactAged snapshots may unnecessarily consume storage space in the cluster.Alert IDA110250Alert TitleAged third-party backup snapshots presentAlert Messagepd_name has num_snapshot aged third-party backup snapshot(s) and they may unnecessarily consume storage space in the cluster.

Check ID110263DescriptionCheck for the old entity-centric third-party backup snapshots.Causes of failureEntity-centric third-party backup snapshots are present in the cluster longer than the configured threshold.ResolutionsThe Recovery Point for the below VM needs to be deleted from Recoverable Entities in Prism Central. If the issue persists, contact Nutanix support.ImpactOld snapshots may unnecessarily consume storage space in the cluster.Alert IDA110263Alert TitleOld Entity-Centric Third-Party Backup Snapshots PresentAlert MessageVM vm_name has num_snapshot old third-party backup snapshot(s) and may unnecessarily consume storage space in the cluster.. The check passes if third-party backup snapshots are not present in the cluster longer than the configured threshold. The default threshold is 7 days, but this threshold value can be modified. The threshold can range from 1 day to 365 days.

Administrators may specify how long a third-party snapshot is expected to be present in the cluster through Prism UI. This check is based on the backup schedule settings. A snapshot is created every time the third-party backup job runs - and the previous snapshot is deleted once the backup job completes. Essentially, there should be 1 snapshot per VM at all times unless otherwise is specified within the backup software. The only other time there will be multiple snapshots for a VM is if that VM is configured within multiple backup jobs.

If the check fails, verify that the threshold set for the check matches the backup schedule and/or retention for the snapshots that are linked to the protection domain. If there are multiple backup jobs linked to the protection domain, then the threshold for this check should be equal to the longest schedule.

For example, if there are 4 backup jobs linked to the protection domain:

Backup Job 1 runs dailyBackup Job 2 runs once a weekBackup Job 3 runs once every 2 weeksBackup Job 4 runs only once a month

The threshold for the check should be set to 32 days. If the threshold is set correctly but the check is still failing, it is recommended to reach out to the third-party backup vendor to ensure the DELETE API calls are being sent. If the snapshots are still present after consulting with the backup vendor, consider engaging Nutanix Support at https://portal.nutanix.com.

Aged snapshots from third-party backups can cause unnecessary capacity utilization on the cluster. Nutanix recommends verifying the threshold is consistent with the expected snapshot time frame within the backup software.

To change the threshold for "Aged third-party backup snapshots present":

Log in to Prism ElementFrom the Home drop-down menu, select "Alerts"In Alerts, click on "Configure" and "Alert Policy"Search for alert ID "A110250" or "Aged third-party backup snapshots present" and click the update policy actionConfigure the alert threshold to be consistent with the retention policy of backup software you are using then click Save

Entity-Centric Snapshots:

The workflow for these snapshots is through Prism Central NOT Prism ElementWorkflow to find entity-centric snapshots. Prism Central UI -> Virtual Infrastructure -> VM Recovery Points -> Select the VM

To change the threshold for "Old Entity-Centric Third-Party Backup Snapshots Present":

Log in to Prism Element where the alert is observedFrom the Home drop-down menu select "Settings"In Settings click "Alert Policy"Search for alert ID "A110263" or "Old Entity-Centric Third-Party Backup Snapshots Present" and click the update policy actionConfigure the alert threshold to be consistent with the retention policy of backup software you are using then click "Save"

NOTE: These checks could also be failing if a VM that was once being backed up via the backup software has been removed from the backup configuration and/or removed from the cluster. It is up to the backup vendor to send the DELETE API call for the snapshot(s) once a VM has been removed from the backup configuration. If you suspect that snapshots are being left on the system due to a VM being removed from the configuration, engage the backup vendor for further assistance.

Default expiration in AOS 5.15.3, 5.18.1 and later

Starting AOS 5.15.3 and 5.18.1, backup snapshots created without an expiration time are assigned a default 60 days expiration. Upgrade AOS to 5.15.3, 5.18.1 or later to prevent this issue in the future. However, upgrading a cluster running a previous version of AOS and having backup snapshots without an expiration date will not change those backup snapshots. They will continue to have no expiration date after the upgrade. In this case, engage the third-party backup vendor. If the snapshots are still present after consulting with the backup vendor, consider engaging Nutanix Support at https://portal.nutanix.com.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.