# Separate stopping NetApp cool tiering from retrieving already cooled data

> A volume-level switch does not undo the capacity-pool setting or automatically return existing cold data.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:00+00:00
- Modified: 2026-09-10T02:14:32+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

A volume-level switch does not undo the capacity-pool setting or automatically return existing cold data.

## Potentially affected

Azure NetApp Files capacity pools and volumes configured for cool access.

## DSE recommendation

Plan tiering cessation, existing-data retrieval, and pool constraints as separate acceptance conditions.

## Article

## Source facts

Disabling cool access at the volume level stops further tiering, but files already in the cool tier remain there. The volume’s retrieval policy remains unchanged when cool access is disabled.

The On-read retrieval policy returns cold data to the hot tier on sequential or random reads; Never serves that data from the cool tier without returning it. A capacity pool enabled for cool access cannot be converted back to a non-cool-access pool. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-netapp-files/manage-cool-access).

## Applicability

Inventory the pool setting, each volume’s tiering state, retrieval policy, and existing cool-tier data. Review service-level movement restrictions in the source before choosing a destination pool. Define whether the objective is stopping new tiering or changing where existing data resides.

## DSE recommendation

DSE recommends agreeing these objectives separately with the workload owner. Preserve the current settings and identify a representative data set before any planned retrieval activity. Avoid describing a disabled checkbox as complete reversal. Keep the pool’s continuing cool-access constraint visible in migration and capacity planning.

## Verification

After an approved change, inspect the volume setting and retrieval policy, then observe the intended reads and resulting tier metrics. Use nonsensitive representative data and document which blocks or files were exercised. Accept the change only against the stated objective; do not infer that all existing cold data returned from a single successful file open.

## Official references

[Microsoft Learn: Manage Azure NetApp Files storage with cool access](https://learn.microsoft.com/en-us/azure/azure-netapp-files/manage-cool-access). Source retrieved September 9, 2026.

## Primary reference

- Name: Manage Azure NetApp Files storage with cool access | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-netapp-files/manage-cool-access
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Separate stopping NetApp cool tiering from retrieving already cooled data,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.