|
| 1 | +--- |
| 2 | +title: Azure Data Box Edge share management | Microsoft Docs |
| 3 | +description: Describes how to use the Azure portal to manage shares on your Azure Data Box Edge. |
| 4 | +services: databox |
| 5 | +author: alkohli |
| 6 | + |
| 7 | +ms.service: databox |
| 8 | +ms.subservice: edge |
| 9 | +ms.topic: overview |
| 10 | +ms.date: 03/11/2019 |
| 11 | +ms.author: alkohli |
| 12 | +--- |
| 13 | +# Use the Azure portal to manage shares on your Azure Data Box Edge |
| 14 | + |
| 15 | +This article describes how to manage shares on your Azure Data Box Edge. You can manage the Azure Data Box Edge via the Azure portal or via the local web UI. Use the Azure portal to add, delete, refresh shares, or sync storage key for storage account associated with the shares. |
| 16 | + |
| 17 | +> [!IMPORTANT] |
| 18 | +> Data Box Edge is in preview. Review the [Azure terms of service for preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) before you order and deploy this solution. |
| 19 | +
|
| 20 | + |
| 21 | +## About shares |
| 22 | + |
| 23 | +To transfer data to Azure, you need to create shares on your Azure Data Box Edge. The shares that you add on the Data Box Edge device can be local shares or shares that push data to cloud. |
| 24 | + |
| 25 | + - **Local shares**: Use these shares when you want the data to be processed locally on the device. |
| 26 | + - **Shares**: Use these shares when you want the device data to be automatically pushed to your storage account in the cloud. All the cloud functions such as **Refresh** and **Sync storage keys** apply to the shares. |
| 27 | + |
| 28 | +In this article, you learn how to: |
| 29 | + |
| 30 | +> [!div class="checklist"] |
| 31 | +> * Add a share |
| 32 | +> * Delete a share |
| 33 | +> * Refresh shares |
| 34 | +> * Sync storage key |
| 35 | +
|
| 36 | + |
| 37 | +## Add a share |
| 38 | + |
| 39 | +Do the following steps in the Azure portal to create a share. |
| 40 | + |
| 41 | +1. In the Azure portal, go to your Data Box Edge resource and then go to **Gateway > Shares**. Select **+ Add share** on the command bar. |
| 42 | + |
| 43 | +  |
| 44 | + |
| 45 | +2. In **Add Share**, specify the share settings. Provide a unique name for your share. |
| 46 | + |
| 47 | + Share names can only contain numbers, lowercase letters, and hyphens. The share name must be between 3 and 63 characters long and begin with a letter or a number. Each hyphen must be preceded and followed by a non-hyphen character. |
| 48 | + |
| 49 | +3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different. |
| 50 | + |
| 51 | +4. Provide a **Storage account** where the share lives. A container is created in the storage account with the share name if the container already does not exist. If the container already exists, then the existing container is used. |
| 52 | + |
| 53 | +5. From the dropdown list, choose the **Storage service** from block blob, page blob, or files. The type of the service chosen depends on which format you want the data to reside in Azure. For example, in this instance, we want the data to reside as block blobs in Azure, hence we select **Block Blob**. If choosing **Page Blob**, you must ensure that your data is 512 bytes aligned. Use **Page blob** for VHDs or VHDX that are always 512 bytes aligned. |
| 54 | + |
| 55 | +6. This step depends on whether you are creating an SMB or an NFS share. |
| 56 | + - **If creating an SMB share** - In the **All privilege local user** field, choose from **Create new** or **Use existing**. If creating a new local user, provide the **username**, **password**, and then confirm password. This assigns the permissions to the local user. After you have assigned the permissions here, you can then use File Explorer to modify these permissions. |
| 57 | + |
| 58 | +  |
| 59 | + |
| 60 | + If you check allow only read operations for this share data, you can specify read-only users. |
| 61 | + - **If creating an NFS share** - You need to supply the **IP addresses of the allowed clients** that can access the share. |
| 62 | + |
| 63 | +  |
| 64 | + |
| 65 | +7. Click **Create** to create the share. You are notified that the share creation is in progress. After the share is created with the specified settings, the **Shares** blade updates to reflect the new share. |
| 66 | + |
| 67 | +## Add a local share |
| 68 | + |
| 69 | +1. In the Azure portal, go to your Data Box Edge resource and then go to **Gateway > Shares**. Select **+ Add share** on the command bar. |
| 70 | + |
| 71 | +  |
| 72 | + |
| 73 | +2. In **Add Share**, specify the share settings. Provide a unique name for your share. |
| 74 | + |
| 75 | + Share names can only contain numbers, lowercase letters, and hyphens. The share name must be between 3 and 63 characters long and begin with a letter or a number. Each hyphen must be preceded and followed by a non-hyphen character. |
| 76 | + |
| 77 | +3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different. |
| 78 | + |
| 79 | +4. To easily access the shares from Edge compute modules, use the local mount point. Select **Use the share with Edge compute** so that the Edge module can use the compute with the local mount point. |
| 80 | + |
| 81 | +5. Select **Configure as Edge local shares**. The data in local shares will stay locally on the device. You can process this data locally. |
| 82 | + |
| 83 | +6. In the **All privilege local user** field, choose from **Create new** or **Use existing**. |
| 84 | + |
| 85 | +7. Select **Create**. |
| 86 | + |
| 87 | +  |
| 88 | + |
| 89 | + You see a notification that the share creation is in progress. After the share is created with the specified settings, the **Shares** blade updates to reflect the new share. |
| 90 | + |
| 91 | +  |
| 92 | + |
| 93 | + Select the share to view the local mountpoint for the Edge compute modules for this share. |
| 94 | + |
| 95 | +  |
| 96 | + |
| 97 | +## Delete a share |
| 98 | + |
| 99 | +Do the following steps in the Azure portal to delete a share. |
| 100 | + |
| 101 | +1. From the list of shares, select and click the share that you want to delete. |
| 102 | + |
| 103 | +  |
| 104 | + |
| 105 | +2. Click **Delete**. |
| 106 | + |
| 107 | +  |
| 108 | + |
| 109 | +3. When prompted for confirmation, click **Yes**. |
| 110 | + |
| 111 | +  |
| 112 | + |
| 113 | +The list of shares updates to reflect the deletion. |
| 114 | + |
| 115 | + |
| 116 | +## Refresh shares |
| 117 | + |
| 118 | +The refresh feature allows you to refresh the contents of a share. When you refresh a share, a search is initiated to find all the Azure objects including blobs and files that were added to the cloud since the last refresh. These additional files are then downloaded to refresh the contents of the share on the device. |
| 119 | + |
| 120 | +> [!IMPORTANT] |
| 121 | +> You can't refresh local shares. |
| 122 | +
|
| 123 | +Do the following steps in the Azure portal to refresh a share. |
| 124 | + |
| 125 | +1. In the Azure portal, go to **Shares**. Select and click the share that you want to refresh. |
| 126 | + |
| 127 | +  |
| 128 | + |
| 129 | +2. Click **Refresh**. |
| 130 | + |
| 131 | +  |
| 132 | + |
| 133 | +3. When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share. |
| 134 | + |
| 135 | +  |
| 136 | + |
| 137 | +4. While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status. |
| 138 | + |
| 139 | +5. The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. The refresh error logs are also updated. |
| 140 | + |
| 141 | +  |
| 142 | + |
| 143 | +If there is a failure, an alert is raised. The alert details the cause and the recommendation to fix the issue. The alert also links to a file that has the complete summary of the failures including the files that failed to update or delete. |
| 144 | + |
| 145 | + |
| 146 | +## Sync storage keys |
| 147 | + |
| 148 | +If your storage account keys have been rotated, then you need to sync the storage access keys. The sync helps the device get the latest keys for your storage account. |
| 149 | + |
| 150 | +Do the following steps in the Azure portal to sync your storage access key. |
| 151 | + |
| 152 | +1. Go to **Overview** in your resource. From the list of shares, choose and click a share associated with the storage account that you need to sync. |
| 153 | + |
| 154 | +  |
| 155 | + |
| 156 | +2. Click **Sync storage key**. Click **Yes** when prompted for confirmation. |
| 157 | + |
| 158 | +  |
| 159 | + |
| 160 | +3. Exit out of the dialog once the sync is complete. |
| 161 | + |
| 162 | +>[!NOTE] |
| 163 | +> You only have to do this once for a given storage account. You don't need to repeat this action for all the shares associated with the same storage account. |
| 164 | +
|
| 165 | + |
| 166 | +## Next steps |
| 167 | + |
| 168 | +- Learn how to [Manage users via Azure portal](data-box-edge-manage-users.md). |
0 commit comments