Check destination hardlinks outside an AzCopy transfer before replacing file content

Source facts

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.

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.

Applicability

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.

DSE recommendation

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.

Verification

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.

Official references

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