Skip to content

Commit 64b7651

Browse files
committed
Fixing some validation issues
1 parent 35af5b6 commit 64b7651

File tree

3 files changed

+20
-20
lines changed

3 files changed

+20
-20
lines changed

articles/storage/blobs/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1340,7 +1340,7 @@ items:
13401340
href: migrate-gen2-wandisco-live-data-platform.md
13411341
- name: Migrate from Data Lake Storage Gen1
13421342
items:
1343-
- name: Migrate using Azure portal
1343+
- name: Migrate using the Azure portal
13441344
href: data-lake-storage-migrate-gen1-to-gen2-azure-portal.md
13451345
- name: Migration guidelines and patterns
13461346
href: data-lake-storage-migrate-gen1-to-gen2.md

articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2-azure-portal.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.service: azure-data-lake-storage
1515
This article shows you how to simplify the migration by using the Azure portal.
1616

1717
> [!NOTE]
18-
> Azure Data Lake Storage Gen1 is now retired. See the retirement announcement [here](https://aka.ms/data-lake-storage-gen1-retirement-announcement).Data Lake Storage Gen1 resources are no longer accessible. If you require special assistance, please [contact us](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
18+
> Azure Data Lake Storage Gen1 is now retired. See the retirement announcement [here](https://aka.ms/data-lake-storage-gen1-retirement-announcement). Data Lake Storage Gen1 resources are no longer accessible. If you require special assistance, please [contact us](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
1919
2020
Here's a video that tells you more about it.
2121

@@ -107,17 +107,17 @@ Whichever option you choose, after you've migrated and verified that all your wo
107107
3. Select the **Migrate data** button.
108108

109109
> [!div class="mx-imgBorder"]
110-
> ![Button to migrate](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-tool.png)
110+
> ![Screenshot of the button to migrate.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-tool.png)
111111
112112
4. Select **Copy data to a new Gen2 account**.
113113

114114
> [!div class="mx-imgBorder"]
115-
> ![Copy data option](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-data-option.png)
115+
> ![Screenshot of the copy data option.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-data-option.png)
116116
117117
5. Give Microsoft consent to perform the data migration by selecting the checkbox. Then, select the **Apply** button.
118118

119119
> [!div class="mx-imgBorder"]
120-
> ![Checkbox to provide consent](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-consent.png)
120+
> ![Screenshot of the checkbox to provide consent.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-consent.png)
121121
122122
A progress bar appears along with a sub status message. You can use these indicators to gauge the progress of the migration. Because the time to complete each task varies, the progress bar won't advance at a consistent rate. For example, the progress bar might quickly advance to 50 percent, but then take a bit more time to complete the remaining 50 percent.
123123

@@ -130,7 +130,7 @@ Whichever option you choose, after you've migrated and verified that all your wo
130130
You can stop the migration at any time by selecting the **Stop migration** button.
131131

132132
> [!div class="mx-imgBorder"]
133-
> ![Stop migration option](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-stop.png)
133+
> ![Screenshot of the stop migration option.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-stop.png)
134134
135135
### Option 2: Perform a complete migration
136136

@@ -141,17 +141,17 @@ Whichever option you choose, after you've migrated and verified that all your wo
141141
3. Select the **Migrate data** button.
142142

143143
> [!div class="mx-imgBorder"]
144-
> ![Migrate button](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-tool.png)
144+
> ![Screenshot of the migrate button.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-tool.png)
145145
146146
4. Select **Complete migration to a new Gen2 account**.
147147

148148
> [!div class="mx-imgBorder"]
149-
> ![Complete migration option](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-complete-option.png)
149+
> ![Screenshot of the complete migration option.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-complete-option.png)
150150
151151
5. Give Microsoft consent to perform the data migration by selecting the checkbox. Then, select the **Apply** button.
152152

153153
> [!div class="mx-imgBorder"]
154-
> ![Consent checkbox](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-consent.png)
154+
> ![Screenshot of the consent checkbox.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-consent.png)
155155
156156
A progress bar appears along with a sub status message. You can use these indicators to gauge the progress of the migration. Because the time to complete each task varies, the progress bar won't advance at a consistent rate. For example, the progress bar might quickly advance to 50 percent, but then take a bit more time to complete the remaining 50 percent.
157157

@@ -168,7 +168,7 @@ Whichever option you choose, after you've migrated and verified that all your wo
168168
You can stop the migration at any time before the URI is redirected by selecting the **Stop migration** button.
169169

170170
> [!div class="mx-imgBorder"]
171-
> ![Migration stop button](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-stop.png)
171+
> ![Screenshot of the migration stop button.](./media/data-lake-storage-migrate-gen1-to-gen2-azure-portal/migration-stop.png)
172172
173173
## Step 6: Verify that the migration completed
174174

@@ -291,7 +291,7 @@ Make sure all your Azure Data lake Analytics accounts are [migrated to Azure Syn
291291

292292
If you used [Option 1: Copy data from Gen1 to Gen2](#option-1-copy-data-from-gen1-to-gen2) mentioned above, then both the Gen1 and Gen2 accounts are available for reads and writes post migration. However, if you used [Option 2: Perform a complete migration](#option-2-perform-a-complete-migration), then going back to the Gen1 account isn't supported. In Option 2, after the migration completes, the data in your Gen1 account won't be accessible and will be deleted after 30 days. You can continue to view the Gen1 account in the Azure portal, and when you're ready, you can delete the Gen1 account.
293293

294-
#### I would like to enable Geo-redundant storage (GRS) on the Gen2-enabled account, how do I do that?
294+
#### I would like to enable Geo-redundant storage (GRS) on the Gen2-enabled account. How do I do that?
295295

296296
Once the migration is complete, both in "Copy data" and "Complete migration" options, you can go ahead and change the redundancy option to GRS as long as you don't plan to use the application compatibility layer. The application compatibility won't work on accounts that use GRS redundancy.
297297

@@ -303,7 +303,7 @@ When we copy the data over to your Gen2-enabled account, we automatically create
303303

304304
When you copy the data over to your Gen2-enabled account, two factors that can affect performance are the number of files and the amount of metadata you have. For example, many small files can affect the performance of the migration.
305305

306-
#### Will WebHDFS File System APIs supported on Gen2 account post migration?
306+
#### Will WebHDFS File System APIs be supported on Gen2 account post-migration?
307307

308308
WebHDFS File System APIs of Gen1 will be supported on Gen2 but with certain deviations, and only limited functionality is supported via the compatibility layer. Customers should plan to leverage Gen2-specific APIs for better performance and features.
309309

articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.service: azure-data-lake-storage
1515
You can migrate your data, workloads, and applications from Azure Data Lake Storage Gen1 to Azure Data Lake Storage Gen2. This article explains the recommended migration approach and covers the different migration patterns and when to use each. For easier reading, this article uses the term *Gen1* to refer to Azure Data Lake Storage Gen1, and the term *Gen2* to refer to Azure Data Lake Storage Gen2.
1616

1717
> [!NOTE]
18-
> Azure Data Lake Storage Gen1 is now retired. See the retirement announcement [here](https://aka.ms/data-lake-storage-gen1-retirement-announcement).Data Lake Storage Gen1 resources are no longer accessible. If you require special assistance, please [contact us](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
18+
> Azure Data Lake Storage Gen1 is now retired. See the retirement announcement [here](https://aka.ms/data-lake-storage-gen1-retirement-announcement). Data Lake Storage Gen1 resources are no longer accessible. If you require special assistance, please [contact us](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
1919
2020

2121
Azure Data Lake Storage Gen2 is built on [Azure Blob storage](storage-blobs-introduction.md) and provides a set of capabilities dedicated to big data analytics. [Data Lake Storage Gen2](https://azure.microsoft.com/services/storage/data-lake-storage/) combines features from [Azure Data Lake Storage Gen1](../../data-lake-store/index.yml), such as file system semantics, directory, and file level security and scale with low-cost, tiered storage, high availability/disaster recovery capabilities from [Azure Blob storage](storage-blobs-introduction.md).
@@ -155,7 +155,7 @@ This is the simplest pattern.
155155
Check out our sample code for the lift and shift pattern in our [Lift and Shift migration sample](https://github.com/Azure/adlsgen1togen2migration/tree/main/3-Migrate/Lift%20and%20Shift).
156156

157157
> [!div class="mx-imgBorder"]
158-
> ![lift and shift pattern](./media/data-lake-storage-migrate-gen1-to-gen2/lift-and-shift.png)
158+
> ![Diagram of the lift and shift pattern.](./media/data-lake-storage-migrate-gen1-to-gen2/lift-and-shift.png)
159159
160160
#### Considerations for using the lift and shift pattern
161161

@@ -181,9 +181,9 @@ Check out our sample code for the lift and shift pattern in our [Lift and Shift
181181
Check out our sample code for the incremental copy pattern in our [Incremental copy migration sample](https://github.com/Azure/adlsgen1togen2migration/tree/main/3-Migrate/Incremental).
182182

183183
> [!div class="mx-imgBorder"]
184-
> ![Incremental copy pattern](./media/data-lake-storage-migrate-gen1-to-gen2/incremental-copy.png)
184+
> ![Diagram of the incremental copy pattern.](./media/data-lake-storage-migrate-gen1-to-gen2/incremental-copy.png)
185185
186-
#### Considerations for using the incremental copy pattern:
186+
#### Considerations for using the incremental copy pattern
187187

188188
- Cutover from Gen1 to Gen2 for all workloads at the same time.
189189

@@ -204,9 +204,9 @@ Check out our sample code for the incremental copy pattern in our [Incremental c
204204
Check out our sample code for the dual pipeline pattern in our [Dual Pipeline migration sample](https://github.com/Azure/adlsgen1togen2migration/tree/main/3-Migrate/Dual%20pipeline).
205205

206206
> [!div class="mx-imgBorder"]
207-
> ![Dual pipeline pattern](./media/data-lake-storage-migrate-gen1-to-gen2/dual-pipeline.png)
207+
> ![Diagram of the dual pipeline pattern.](./media/data-lake-storage-migrate-gen1-to-gen2/dual-pipeline.png)
208208
209-
#### Considerations for using the dual pipeline pattern:
209+
#### Considerations for using the dual pipeline pattern
210210

211211
- Gen1 and Gen2 pipelines run side-by-side.
212212

@@ -225,9 +225,9 @@ Check out our sample code for the dual pipeline pattern in our [Dual Pipeline mi
225225
Check out our sample code for the bidirectional sync pattern in our [Bidirectional Sync migration sample](https://github.com/Azure/adlsgen1togen2migration/tree/main/3-Migrate/Bi-directional).
226226

227227
> [!div class="mx-imgBorder"]
228-
> ![Bidirectional pattern](./media/data-lake-storage-migrate-gen1-to-gen2/bidirectional-sync.png)
228+
> ![Diagram of the bidirectional pattern.](./media/data-lake-storage-migrate-gen1-to-gen2/bidirectional-sync.png)
229229
230-
#### Considerations for using the bi-directional sync pattern:
230+
#### Considerations for using the bi-directional sync pattern
231231

232232
- Ideal for complex scenarios that involve a large number of pipelines and dependencies where a phased approach might make more sense.
233233

0 commit comments

Comments
 (0)