An administrator ha having difficulty enabling Data Lens for a file server. What is the most likely cause of this issue?

According to official Nutanix documentation, a primary limitation for enabling Data Lens is that it cannot be activated on a cloned file server. The cloning process creates a new file server instance with certain properties that are incompatible with the Data Lens integration and initialization process. To use Data Lens, the administrator must use the original file server or deploy a new, non-cloned file server. This restriction ensures the unique identity and configuration integrity required for the Data Lens analytics service to function correctly.

A. The file server has blacklisted file types.

Blacklisting files is a storage policy to control data types and does not prevent the enablement of the Data Lens analytics service itself.

B. SSR is enabled on the file server.

Self-Service Restore (SSR) is a data recovery feature that is fully compatible with Data Lens and does not interfere with its activation.

D. The file server is in a Protection Domain.

Placing a file server in a Protection Domain for disaster recovery is a supported configuration and does not prevent an administrator from enabling Data Lens.

1. Nutanix Data Lens Guide v2.3

Section: "Enabling Data Lens".

Under the prerequisites and limitations for enabling the service

the guide explicitly states: "You cannot enable Data Lens on a cloned file server." This directly confirms that a cloned file server is the cause of the issue.

2. Nutanix University: NCP-US 6.5 Study Guide

Chapter 5: "Nutanix Files".

This official study material discusses the features and limitations of Nutanix Files. It clarifies that while features like SSR (Self-Service Restore) and Protection Domain integration are standard

certain advanced services have specific deployment prerequisites

reinforcing that not all file server states (like being cloned) are compatible with all add-on services.