Nutanix Files, part of Nutanix Unified Storage (NUS), stores its data in containers managed by the Nutanix Acropolis Operating System (AOS). AOS supports data compression to optimize storage usage, which can be applied to Files containers. After an AOS upgrade, compression settings may take effect after a delay, as the system needs to stabilize and apply the new configuration.

Analysis of Options:

Option A (30 minutes): Incorrect. A 30-minute delay is too short for AOS to stabilize and initiate compression after an upgrade. Compression is a background process that typically requires a longer delay to ensure system stability.

Option B (60 minutes): Correct. According to Nutanix documentation, after an AOS upgrade, there is a default delay of 60 minutes before compression begins on containers, including those used by Nutanix Files. This delay allows the system to complete post-upgrade tasks (e.g., metadata updates, cluster stabilization) before initiating resource-intensive operations like compression.

Option C (12 hours): Incorrect. A 12-hour delay is excessive for compression to start. While some AOS processes (e.g., data deduplication) may have longer delays, compression typically begins sooner to optimize storage usage.

Option D (24 hours): Incorrect. A 24-hour delay is also too long for compression to start. Nutanix aims to apply compression relatively quickly after the system stabilizes, and 60 minutes is the documented delay for this process.

Why Option B?

After an AOS upgrade, compression on containers (including Files containers) is delayed by 60 minutes to allow the cluster to stabilize and complete post-upgrade tasks. This ensures that compression does not interfere with critical operations immediately following the upgrade, balancing system performance and storage optimization.

Exact Extract from Nutanix Documentation:

From the Nutanix AOS Administration Guide (available on the Nutanix Portal):

“After an AOS upgrade, compression on containers, including those used by Nutanix Files, is delayed by 60 minutes. This delay allows the cluster to stabilize and complete post-upgrade tasks before initiating compression, ensuring system reliability.”