{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "slug": "dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data", "url": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/" }, "title": "Separate stopping NetApp cool tiering from retrieving already cooled data", "summary": "A volume-level switch does not undo the capacity-pool setting or automatically return existing cold data.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:22:00+00:00", "modified_at": "2026-09-10T02:14:32+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 235, "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.", "primary_source": { "name": "Manage Azure NetApp Files storage with cool access | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/manage-cool-access", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Manage Azure NetApp Files storage with cool access. Source retrieved September 9, 2026.

", "content_text": "Source facts\nDisabling 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.\nThe 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.\nApplicability\nInventory 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.\nDSE recommendation\nDSE 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Manage Azure NetApp Files storage with cool access. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nDisabling 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.\n\nThe 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).\n\n## Applicability\n\nInventory 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nAfter 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "url": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate stopping NetApp cool tiering from retrieving already cooled data", "item": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "url": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/", "headline": "Separate stopping NetApp cool tiering from retrieving already cooled data", "description": "A volume-level switch does not undo the capacity-pool setting or automatically return existing cold data.", "abstract": "A volume-level switch does not undo the capacity-pool setting or automatically return existing cold data.", "articleBody": "Source facts\nDisabling 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.\nThe 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.\nApplicability\nInventory 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.\nDSE recommendation\nDSE 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Manage Azure NetApp Files storage with cool access. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:22:00+00:00", "dateModified": "2026-09-10T02:14:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-596-separate-stopping-netapp-cool-tiering-from-retrieving-already-cooled-data/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Separate stopping NetApp cool tiering from retrieving already cooled data" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 235, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Manage Azure NetApp Files storage with cool access | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/manage-cool-access" } } ] } }