{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "slug": "dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file", "url": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/" }, "title": "Check destination hardlinks outside an AzCopy transfer before replacing file content", "summary": "With hardlink preservation, Azure Files NFS uploads update existing linked paths differently from downloads to a local filesystem.", "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": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "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:25:11+00:00", "modified_at": "2026-09-10T02:04:57+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 238, "potentially_affected": "AzCopy transfers involving Azure Files NFS with hardlink-preserving source and destination filesystems.", "dse_recommendation": "Include pre-existing destination links outside the selected transfer in the fidelity test.", "primary_source": { "name": "Transfer data to or from Azure Files by using AzCopy v10 | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files", "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

With –hardlinks=preserve, uploads and service-to-service transfers into Azure Files NFS write content in place. Existing destination hardlinks outside the transfer continue to reference the updated data.

\n

Downloads to a local filesystem use a temporary file followed by rename. Destination hardlinks outside that transfer retain the original inode and stale data instead of following the replacement. Hardlink preservation requires support on both source and destination filesystems. Microsoft Learn.

\n

Applicability

\n

LocalFileNFS uploads and FileNFSLocal downloads require local Linux; FileNFSFileNFS service-to-service transfers can run from Windows, Linux or macOS. Identify the transfer direction, selected paths and any other destination paths linked to the same file before planning the transfer.

\n

DSE recommendation

\n

DSE recommends treating out-of-scope hardlinks as part of the impact review even when their path names are not selected for copying. Decide whether they should observe new or old content and choose an approved transfer approach accordingly. Do not assume the preservation flag gives identical replacement behavior for uploads and downloads.

\n

Verification

\n

Use harmless files with known link relationships at both endpoints. Replace one selected path through the approved transfer, then inspect content and file identity through every related path, including those outside the transfer. Record whether links share the new data or retain the old content. Resolve any mismatch with the application owner’s expectations before moving production data.

\n

Official references

\n

Microsoft Learn: Transfer data to or from Azure Files by using AzCopy v10. Source retrieved September 9, 2026.

", "content_text": "Source facts\nWith –hardlinks=preserve, uploads and service-to-service transfers into Azure Files NFS write content in place. Existing destination hardlinks outside the transfer continue to reference the updated data.\nDownloads to a local filesystem use a temporary file followed by rename. Destination hardlinks outside that transfer retain the original inode and stale data instead of following the replacement. Hardlink preservation requires support on both source and destination filesystems. Microsoft Learn.\nApplicability\nLocalFileNFS uploads and FileNFSLocal downloads require local Linux; FileNFSFileNFS service-to-service transfers can run from Windows, Linux or macOS. Identify the transfer direction, selected paths and any other destination paths linked to the same file before planning the transfer.\nDSE recommendation\nDSE recommends treating out-of-scope hardlinks as part of the impact review even when their path names are not selected for copying. Decide whether they should observe new or old content and choose an approved transfer approach accordingly. Do not assume the preservation flag gives identical replacement behavior for uploads and downloads.\nVerification\nUse harmless files with known link relationships at both endpoints. Replace one selected path through the approved transfer, then inspect content and file identity through every related path, including those outside the transfer. Record whether links share the new data or retain the old content. Resolve any mismatch with the application owner’s expectations before moving production data.\nOfficial references\nMicrosoft Learn: Transfer data to or from Azure Files by using AzCopy v10. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nWith –hardlinks=preserve, uploads and service-to-service transfers into Azure Files NFS write content in place. Existing destination hardlinks outside the transfer continue to reference the updated data.\n\nDownloads to a local filesystem use a temporary file followed by rename. Destination hardlinks outside that transfer retain the original inode and stale data instead of following the replacement. Hardlink preservation requires support on both source and destination filesystems. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files).\n\n## Applicability\n\nLocalFileNFS uploads and FileNFSLocal downloads require local Linux; FileNFSFileNFS service-to-service transfers can run from Windows, Linux or macOS. Identify the transfer direction, selected paths and any other destination paths linked to the same file before planning the transfer.\n\n## DSE recommendation\n\nDSE recommends treating out-of-scope hardlinks as part of the impact review even when their path names are not selected for copying. Decide whether they should observe new or old content and choose an approved transfer approach accordingly. Do not assume the preservation flag gives identical replacement behavior for uploads and downloads.\n\n## Verification\n\nUse harmless files with known link relationships at both endpoints. Replace one selected path through the approved transfer, then inspect content and file identity through every related path, including those outside the transfer. Record whether links share the new data or retain the old content. Resolve any mismatch with the application owner’s expectations before moving production data.\n\n## Official references\n\n[Microsoft Learn: Transfer data to or from Azure Files by using AzCopy v10](https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files). 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-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "url": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check destination hardlinks outside an AzCopy transfer before replacing file content", "item": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "url": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/", "headline": "Check destination hardlinks outside an AzCopy transfer before replacing file content", "description": "With hardlink preservation, Azure Files NFS uploads update existing linked paths differently from downloads to a local filesystem.", "abstract": "With hardlink preservation, Azure Files NFS uploads update existing linked paths differently from downloads to a local filesystem.", "articleBody": "Source facts\nWith –hardlinks=preserve, uploads and service-to-service transfers into Azure Files NFS write content in place. Existing destination hardlinks outside the transfer continue to reference the updated data.\nDownloads to a local filesystem use a temporary file followed by rename. Destination hardlinks outside that transfer retain the original inode and stale data instead of following the replacement. Hardlink preservation requires support on both source and destination filesystems. Microsoft Learn.\nApplicability\nLocalFileNFS uploads and FileNFSLocal downloads require local Linux; FileNFSFileNFS service-to-service transfers can run from Windows, Linux or macOS. Identify the transfer direction, selected paths and any other destination paths linked to the same file before planning the transfer.\nDSE recommendation\nDSE recommends treating out-of-scope hardlinks as part of the impact review even when their path names are not selected for copying. Decide whether they should observe new or old content and choose an approved transfer approach accordingly. Do not assume the preservation flag gives identical replacement behavior for uploads and downloads.\nVerification\nUse harmless files with known link relationships at both endpoints. Replace one selected path through the approved transfer, then inspect content and file identity through every related path, including those outside the transfer. Record whether links share the new data or retain the old content. Resolve any mismatch with the application owner’s expectations before moving production data.\nOfficial references\nMicrosoft Learn: Transfer data to or from Azure Files by using AzCopy v10. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:11+00:00", "dateModified": "2026-09-10T02:04:57+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/" }, "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-405-check-destination-hardlinks-outside-an-azcopy-transfer-before-replacing-file/#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": "Check destination hardlinks outside an AzCopy transfer before replacing file content" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 238, "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": "Transfer data to or from Azure Files by using AzCopy v10 | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files" } } ] } }