Skip to content

Latest commit

 

History

History
100 lines (58 loc) · 6.09 KB

File metadata and controls

100 lines (58 loc) · 6.09 KB
title Preserving file ACLs, attributes, and timestamps with Azure Data Box
description ACLs, timestamps, and attributes preserved during data copy via SMB to Azure Data Box. Copying metadata with Windows and Linux data copy tools.
services databox
author stevenmatthew
ms.service azure-databox
ms.custom linux-related-content
ms.topic concept-article
ms.date 11/18/2022
ms.author shaas

Preserving file ACLs, attributes, and timestamps with Azure Data Box

Azure Data Box lets you preserve access control lists (ACLs), timestamps, and file attributes when sending data to Azure. This article describes the metadata that you can transfer when copying data to Data Box via Server Message Block (SMB) to upload it to Azure Files.

Transferred metadata

ACLs, timestamps, and file attributes are the metadata that is transferred when the data from Data Box is uploaded to Azure Files. In this article, ACLs, timestamps, and file attributes are referred to collectively as metadata.

The metadata can be copied with Windows and Linux data copy tools. Metadata isn't preserved when transferring data to blob storage. Metadata is also not transferred when copying data over NFS.

The subsequent sections of the article discuss in detail as to how the timestamps, file attributes, and ACLs are transferred when the data from Data Box is uploaded to Azure Files.

[!INCLUDE data-box-transferred-metadata]

ACLs

Depending on the transfer method used and whether you're using a Windows or Linux client, some or all discretionary and default access control lists (ACLs) on files and folders may be transferred during the data copy to Azure Files.

Transfer of ACLs is enabled by default. You might want to disable this setting in the local web UI on your Data Box. For more information, see Use the local web UI to administer your Data Box and Data Box Heavy.

Note

Files with ACLs containing conditional access control entry (ACE) strings are not copied. This is a known issue. To work around this, copy these files to the Azure Files share manually by mounting the share and then using a copy tool that supports copying ACLs.

ACLs transfer over SMB

During an SMB file transfer, the following ACLs are transferred:

  • Discretionary ACLs (DACLs) and system ACLs (SACLs) for directories and files that you copy to your Data Box.
  • If you use a Linux client, only Windows NT ACLs are transferred.

ACLs transfer over Data Copy Service

During a data copy service file transfer, the following ACLs are transferred:

  • Discretionary ACLs (DACLs) and system ACLs (SACLs) for directories and files that you copy to your Data Box.

To copy SACLs from your files, you must provide credentials for a user with SeBackupPrivilege. Users in the Administrators or Backup Operators group will have this privilege by default

If you do not have SeBackupPrivilege:

  • You will not be able to copy SACLs for Azure Files copy service jobs.
  • You may experience access issues and receive this error in the error log: Could not read SACLs from share due to insufficient privileges.

For more information, learn more about SeBackupPrivilege.

ACLs transfer over NFS

ACLs (and metadata attributes) aren't transferred when you copy data over NFS.

Default ACLs transfer

Even if your data copy tool doesn't copy ACLs, the default ACLs on directories and files are transferred to Azure Files when you use a Windows client. The default ACLs aren't transferred when you use a Linux client.

The following default ACLs are transferred:

  • Account permissions:

    • Built-in Administrator account
    • SYSTEM account
    • SMB share user account used to mount and copy data in the Data Box
  • Security descriptors with these properties: DACL, Owner, Group, SACL

[!INCLUDE data-box-copy-data-and-metadata]

Next steps