Links and directories copied by Amazon DataSync - Amazon DataSync
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

On December 7, 2023, we discontinued version 1 DataSync agents. Check the Agents page on the DataSync console to see if you have affected agents. If you do, replace those agents or delete them if they aren't in use. If you need more help, contact Amazon Web Services Support.

Links and directories copied by Amazon DataSync

Amazon DataSync handles copied hard links, symbolic links, and directories differently depending on the storage locations involved in your transfer.

Here's how DataSync handles hard links in some common transfer scenarios:

  • When copying between an NFS file server, FSx for Lustre, FSx for OpenZFS, FSx for ONTAP (using NFS), and Amazon EFS, hard links are preserved.

  • When copying to Amazon S3, each underlying file referenced by a hard link is transferred only once. During incremental copies, separate objects are created in your S3 bucket. If a hard link is unchanged in Amazon S3, it's correctly restored when transferred to an NFS file server, FSx for Lustre, FSx for OpenZFS, FSx for ONTAP (using NFS), or Amazon EFS file system.

  • When copying to Microsoft Azure Blob Storage, each underlying file referenced by a hard link is transferred only once. During incremental copies, separate objects are created in your blob storage if there are new references in the source. When copying from Azure Blob Storage, DataSync transfers hard links as if they are individual files.

  • When copying between an SMB file server, FSx for Windows File Server, and FSx for ONTAP (using SMB), hard links aren't supported. If DataSync encounters hard links in these situations, the transfer task completes with an error. To learn more, check your CloudWatch logs.

  • When copying to HDFS, hard links aren't supported. CloudWatch logs show these links as skipped.

Here's how DataSync handles symbolic links in some common transfer scenarios:

  • When copying between an NFS file server, FSx for Lustre, FSx for OpenZFS, FSx for ONTAP (using NFS), and Amazon EFS, symbolic links are preserved.

  • When copying to Amazon S3, the link target path is stored in the Amazon S3 object. The link is correctly restored when transferred to an NFS file server, FSx for Lustre, FSx for OpenZFS, FSx for ONTAP, or Amazon EFS file system.

  • When copying to Azure Blob Storage, symbolic links aren't supported. CloudWatch logs show these links as skipped.

  • When copying between an SMB file server, FSx for Windows File Server, and FSx for ONTAP (using SMB), symbolic links aren't supported. If DataSync encounters symbolic links in these situations, the task completes with an error. To learn more, check your CloudWatch logs.

  • When copying to HDFS, symbolic links aren't supported. CloudWatch logs show these links as skipped.

Directories

In general, DataSync preserves directories when transferring between storage systems. This isn’t the case in the following situations:

  • When copying to Amazon S3, directories are represented as empty objects that have prefixes and end with a forward slash (/).

  • When copying to Azure Blob Storage without a hierarchical namespace, directories don't exist. What looks like a directory is just part of an object name.