You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/databox/data-box-deploy-copy-data-via-nfs.md
+16-10Lines changed: 16 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,20 +36,20 @@ Before you begin, make sure that:
36
36
## Connect to Data Box
37
37
38
38
Based on the storage account selected, Data Box creates up to:
39
-
- Three shares for each associated storage account for GPv1 and GPv2.
40
-
- One share for premium storage.
41
-
- One share for blob storage account.
39
+
40
+
* Three shares for each associated storage account for GPv1 and GPv2.
41
+
* One share for premium storage.
42
+
* Four shares for a blob storage account.
42
43
43
44
Under block blob and page blob shares, first-level entities are containers, and second-level entities are blobs. Under shares for Azure Files, first-level entities are shares, second-level entities are files.
44
45
45
46
The following table shows the UNC path to the shares on your Data Box and Azure Storage path URL where the data is uploaded. The final Azure Storage path URL can be derived from the UNC share path.
If you are using a Linux host computer, perform the following steps to configure Data Box to allow access to NFS clients.
55
55
@@ -75,7 +75,13 @@ If you are using a Linux host computer, perform the following steps to configure
75
75
76
76
`sudo mount -t nfs -o sec=sys,resvport 10.161.23.130:/Mystoracct_Blob /home/databoxubuntuhost/databox`
77
77
78
-
**Always create a folder for the files that you intend to copy under the share and then copy the files to that folder**. The folder created under block blob and page blob shares represents a container to which data is uploaded as blobs. You cannot copy files directly to *root* folder in the storage account.
78
+
79
+
> [!IMPORTANT]
80
+
> You can't copy files directly to the storage account's *root* folder. Within a block blob storage account's root folder, you'll find a folder corresponding to each of the available access tiers.
81
+
>
82
+
> To copy you data to Azure Data Box, you must first select the folder corresponding to one of the access tiers. Next, create a sub-folder within that tier's folder to store your data. Finally, copy your data to the newly created sub-folder. Your new sub-folder represents the container created within the storage account during ingestion. Your data is uploaded to this container as blobs.
83
+
84
+
<!--**Always create a folder for the files that you intend to copy under the share and then copy the files to that folder**. The folder created under block blob and page blob shares represents a container to which data is uploaded as blobs. You cannot copy files directly to *root* folder in the storage account.-->
79
85
80
86
## Copy data to Data Box
81
87
@@ -88,7 +94,7 @@ Once you are connected to the Data Box shares, the next step is to copy data. Be
88
94
* Use different storage accounts for SMB and NFS.
89
95
* Don't copy the same data to the same end destination in Azure using both SMB and NFS. In these cases, the final outcome can't be determined.
90
96
* Although copying via both SMB and NFS in parallel can work, we don't recommend doing that as it's prone to human error. Wait until your SMB data copy is complete before you start an NFS data copy.
91
-
***Always create a folder for the files that you intend to copy under the share and then copy the files to that folder**. The folder created under block blob and page blob shares represents a container to which data is uploaded as blobs. You cannot copy files directly to *root* folder in the storage account.
97
+
*When copying data to the block blob share, create a sub-folder within the desired access tier, then copy data to the newly created sub-folder. The sub-folder represents a container to which your data is uploaded as blobs. You cannot copy files directly to the*root* folder in the storage account.
92
98
* If ingesting case-sensitive directory and file names from an NFS share to NFS on Data Box:
Replace `<key>` with your account key. To get your account key, in the Azure portal, go to your storage account. Go to **Settings > Access keys**, select a key, and paste it into the AzCopy command.
@@ -218,7 +218,7 @@ If you only want to copy source resources that do not exist in the destination,
Copy file name to clipboardExpand all lines: articles/databox/data-box-deploy-copy-data.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ Based on the storage account selected, Data Box creates up to:
57
57
58
58
<!--Under block blob and page blob shares, first-level entities are containers, and second-level entities are blobs. Under shares for Azure Files, first-level entities are shares, second-level entities are files.-->
59
59
60
-
Within block blob and page blob shares, first-level entities are folders for each access tier type. Second-level entities are containers, and third-level entities are blobs. Under shares for Azure Files, first-level entities are shares, second-level entities are files.
60
+
Within a block blob share, the first-level entity is a folder for each access tier type. Second-level entities are containers, and third-level entities are blobs. Under all other shares, first-level entities are shares, second-level entities are files.
61
61
62
62
The following table shows the UNC path to the shares on your Data Box and the corresponding Azure Storage path URL where the data is uploaded. The final Azure Storage path URL can be derived from the UNC share path.
63
63
@@ -108,7 +108,7 @@ If using a Windows Server host computer, follow these steps to connect to the Da
108
108
> [!IMPORTANT]
109
109
> You can't copy files directly to the storage account's *root* folder. Within a block blob storage account's root folder, you'll find a folder corresponding to each of the available access tiers.
110
110
>
111
-
> To copy you data to Azure Data Box, you must first select the folder corresponding to one of the access tiers. Next, create a sub-folder within that tier's folder to store your data. Finally, copy your data to the newly created sub-folder. Your new sub-folder represents the container created within the storage account during ingestion. Your data is uploaded to this container as blobs.
111
+
> To copy your data to Azure Data Box, you must first select the folder corresponding to one of the access tiers. Next, create a sub-folder within that tier's folder to store your data. Finally, copy your data to the newly created sub-folder. Your new sub-folder represents the container created within the storage account during ingestion. Your data is uploaded to this container as blobs.
112
112
113
113
If using a Linux client, use the following command to mount the SMB share. The `vers` parameter below is the version of SMB that your Linux host supports. Insert the appropriate version into the sample command below. To see a list of SMB versions supported by Data Box, see [Supported file systems for Linux clients](./data-box-system-requirements.md#supported-file-transfer-protocols-for-clients)
114
114
@@ -331,3 +331,5 @@ Advance to the next tutorial to learn how to ship your Data Box back to Microsof
331
331
> [Ship your Azure Data Box to Microsoft](./data-box-deploy-picked-up.md)
Copy file name to clipboardExpand all lines: articles/databox/data-box-disk-deploy-copy-data.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,13 +59,14 @@ Before you begin, make sure that:
59
59
60
60
Review the following considerations before you copy the data to the disks:
61
61
62
-
- It is your responsibility to ensure that you copy your local data to the folders that correspond to the appropriate data format. For instance, copy block blob data to the *BlockBlob* folder. Block blobs being archived should be copied to the *BlockBlob_Archive* folder. If the local data format doesn't match the appropriate folder for the chosen storage type, the data upload to Azure fails in a later step.
63
-
- While copying data, ensure that the data size conforms to the size limits described within in the [Azure storage and Data Box Disk limits](data-box-disk-limits.md) article.
64
-
- To preserve metadata such as ACLs, timestamps, and file attributes when transferring data to Azure Files, follow the guidance within the [Preserving file ACLs, attributes, and timestamps with Azure Data Box Disk](data-box-disk-file-acls-preservation.md) article.
65
-
- If you use both Data Box Disk and other applications to upload data simultaneously, you may experience upload job failures and data corruption.
62
+
- It is your responsibility to ensure that you copy your local data to the folders that correspond to the appropriate data format. For instance, copy block blob data to the folder corrresponding to the appropriate access tier within the *BlockBlob* folder. Frequently used block blobs should be copies to the *Hot* tier's folder within *BlockBlob*. Blobs being archived should be copied to the *BlockBlob_Archive* folder. If the local data format doesn't match the appropriate folder for the chosen storage type, the data upload to Azure fails in a later step.
66
63
67
64
> [!IMPORTANT]
68
65
> Data uploaded to the archive tier remains offline and needs to be rehydrated before reading or modifying. Data copied to the archive tier must remain for at least 180 days or be subject to an early deletion charge. Archive tier is not supported for ZRS, GZRS, or RA-GZRS accounts.
66
+
67
+
- While copying data, ensure that the data size conforms to the size limits described within in the [Azure storage and Data Box Disk limits](data-box-disk-limits.md) article.
68
+
- To preserve metadata such as ACLs, timestamps, and file attributes when transferring data to Azure Files, follow the guidance within the [Preserving file ACLs, attributes, and timestamps with Azure Data Box Disk](data-box-disk-file-acls-preservation.md) article.
69
+
- If you use both Data Box Disk and other applications to upload data simultaneously, you may experience upload job failures and data corruption.
69
70
70
71
> [!IMPORTANT]
71
72
> If you specified managed disks as one of the storage destinations during order creation, the following section is applicable.
@@ -81,23 +82,23 @@ Perform the following steps to connect and copy data from your computer to the D
81
82
82
83
|Selected storage destination |Storage account type|Staging storage account type |Folders and subfolders |
The following screenshot shows an order where a GPv2 storage account and archive tier were specified:
91
92
92
93
:::image type="content" source="media/data-box-disk-deploy-copy-data/content-sml.png" alt-text="Screenshot of the contents of the disk drive." lightbox="media/data-box-disk-deploy-copy-data/content.png":::
93
94
94
-
1. Copy data to be imported as block blobs into the *BlockBlob* folder. Copy data to be stored as block blobs with the archive tier into the *BlockBlob_Archive* folder. Similarly, copy VHD or VHDX data to the *PageBlob* folder, and file share data into *AzureFile* folder.
95
+
1.Copy VHD or VHDX data to the *PageBlob* folder. All files copied to the *PageBlob* folder are copied into a default `$root` container within the Azure Storage account. A container is created in the Azure storage account for each subfolder within the *PageBlob* folder.
95
96
96
-
A container is created in the Azure storage account for each subfolder within the *BlockBlob* and *PageBlob* folders. All files copied to the *BlockBlob* and *PageBlob* folders are copied into a default `$root`container within the Azure Storage account. Any files in the `$root` container are always uploaded as block blobs.
97
+
Copy data to be placed in Azure file shares to a subfolder within the *AzureFile* folder. All files copied to the *AzureFile* folder are copied as files to a default container of type `databox-format-[GUID]`, for example, `databox-azurefile-7ee19cfb3304122d940461783e97bf7b4290a1d7`.
97
98
98
-
Copy data to be placed in Azure file shares to a subfolder within the *AzureFile* folder. All files copied to the *AzureFile*folder are copied as files to a default container of type `databox-format-[GUID]`, for example, `databox-azurefile-7ee19cfb3304122d940461783e97bf7b4290a1d7`.
99
+
You can't copy files directly to the *BlockBlob*'s *root* folder. Within the root folder, you'll find a sub-folder corresponding to each of the available access tiers. To copy your blob data, you must first select the folder corresponding to one of the access tiers. Next, create a sub-folder within that tier's folder to store your data. Finally, copy your data to the newly created sub-folder. Your new sub-folder represents the container created within the storage account during ingestion. Your data is uploaded to this container as blobs. As with the *AzureFile* share, a new blob storage container will be created for each sub-folder located at the *BlockBlob*'s *root* folder. The data within these folders will be saved according to the storage account's default access tier.
99
100
100
-
Before you begin to copy data, you need to move any files and folders that exist in the root directory to a different folder.
101
+
Before you begin to copy data, you need to move any files and folders that exist in the root directory to a different folder.
101
102
102
103
> [!IMPORTANT]
103
104
> All the containers, blobs, and filenames should conform to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). If these rules are not followed, the data upload to Azure will fail.
0 commit comments