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-heavy-deploy-copy-data.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,6 @@ In this tutorial, you learn how to:
38
38
39
39
> [!div class="checklist"]
40
40
> * Connect to Data Box Heavy
41
-
> * Determine appropriate access tiers for block blobs
42
41
> * Copy data to Data Box Heavy
43
42
44
43
::: zone-end
@@ -62,11 +61,11 @@ Before you begin, make sure that:
62
61
3. You have a host computer that has the data that you want to copy over to Data Box Heavy. Your host computer must:
63
62
- Run a [Supported operating system](data-box-system-requirements.md).
64
63
- Be connected to a high-speed network. For fastest copy speeds, two 40-GbE connections (one per node) can be utilized in parallel. If you do not have 40-GbE connection available, we recommend that you have at least two 10-GbE connections (one per node).
65
-
66
64
67
65
## Connect to Data Box Heavy shares
68
66
69
67
Based on the storage account selected, Data Box Heavy creates up to:
68
+
70
69
- Three shares for each associated storage account for GPv1 and GPv2.
71
70
- One share for premium storage.
72
71
- One share for a blob storage account, containing one folder for each of the four access tiers.
@@ -79,6 +78,14 @@ The following table identifies the names of the Data Box shares to which you can
You can't copy files directly to the *root* folder of any Data Box share. Instead, create folders within the Data Box share depending on your use case.
82
+
83
+
Block blobs support the assignment of access tiers at the file level. When copying files to the block blob share, the recommended best-practice is to add new subfolders within the appropriate access tier. After creating new subfolders, continue adding files to each subfolder as appropriate.
84
+
85
+
A new container is created for any folder residing at the root of the block blob share. Any file within that folder is copied to the storage account's default access tier as a block blob.
86
+
87
+
For more information about blob access tiers, see [Access tiers for blob data](../storage/blobs/access-tiers-overview.md). For more detailed information about access tier best practices, see [Best practices for using blob access tiers](../storage/blobs/access-tiers-best-practices.md).
88
+
82
89
The following table shows the UNC path to the shares on your Data Box and the corresponding Azure Storage path URL to which data is uploaded. The final Azure Storage path URL can be derived from the UNC share path.
83
90
84
91
| Azure Storage types | Data Box shares |
@@ -87,16 +94,8 @@ The following table shows the UNC path to the shares on your Data Box and the co
Note that you can't copy files directly to the *root* folder of any Data Box share. Instead, create folders within the Data Box share depending on your use case.
91
-
92
-
Block blobs support the assignment of access tiers at the file level. When copying files to the block blob share, the recommended best-practice is to add new subfolders within the appropriate access tier. After creating new subfolders, continue adding files to each subfolder as appropriate.
93
-
94
-
A new container is created for any folder residing at the root of the block blob share. Any file within that folder is copied to the storage account's default access tier as a block blob.
95
-
96
97
For more information about blob access tiers, see [Access tiers for blob data](../storage/blobs/access-tiers-overview.md). For more detailed information about access tier best practices, see [Best practices for using blob access tiers](../storage/blobs/access-tiers-best-practices.md).
97
98
98
-
The following table shows the UNC path to the shares on your Data Box and the corresponding Azure Storage path URL to which data is uploaded. The final Azure Storage path URL can be derived from the UNC share path.
99
-
100
99
The steps to connect using a Windows or a Linux client are different.
0 commit comments