Skip to content

Commit ae71f75

Browse files
committed
More acrolinx fixes.
1 parent 9303e92 commit ae71f75

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/storage/files/migrate-files-between-shares.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,7 @@ author: khdownie
99
---
1010

1111
# Migrate files from one SMB Azure file share to another
12-
13-
This article describes how to migrate files between SMB Azure file shares. One common reason to do this is if you need to migrate from an HDD file share to an SSD file share to get increased performance for your application workload.
12+
This article describes how to migrate files between SMB file shares hosted in Azure Files. You can use this method to migrate between HDD and SSD file shares, file shares using a different billing model, or file shares in different regions.
1413

1514
> [!WARNING]
1615
> If you're using Azure File Sync, the migration process is different than described in this article. Instead, see [Migrate files from one Azure file share to another when using Azure File Sync](../file-sync/file-sync-share-to-share-migration.md).
@@ -27,17 +26,16 @@ This article describes how to migrate files between SMB Azure file shares. One c
2726
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Local (LRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
2827
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Zone (ZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
2928
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Geo (GRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
30-
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | GeoZone (GZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) ||
29+
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | GeoZone (GZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
3130

3231
## Migrate using Robocopy
33-
3432
Follow these steps to migrate using Robocopy, a command-line file copy utility included with Windows.
3533

3634
1. Deploy a Windows virtual machine (VM) in Azure in the same region as your source file share. Keeping the data and networking in Azure is faster and avoids outbound data transfer charges. For optimal performance, we recommend a multi-core VM type with at least 56 GiB of memory, for example **Standard_DS5_v2**.
3735

38-
1. Mount both the source and target file shares to the VM. Be sure to mount them using the storage account key to make sure the VM has access to all the files. Don't use a domain identity.
36+
2. Mount both the source and target file shares to the VM. Be sure to mount them using the storage account key to make sure the VM has access to all the files. Don't use a domain identity.
3937

40-
1. Run this command at the Windows command prompt. Optionally, you can include flags for logging features as a best practice (/NP, /NFL, /NDL, /UNILOG).
38+
3. Run this command at the Windows command prompt. Optionally, you can include flags for logging features as a best practice (/NP, /NFL, /NDL, /UNILOG).
4139

4240
```console
4341
robocopy <source> <target> /MIR /COPYALL /MT:16 /R:2 /W:1 /B /IT /DCOPY:DAT
@@ -51,9 +49,9 @@ Follow these steps to migrate using Robocopy, a command-line file copy utility i
5149

5250
You can run the command while your source is still online, but IOPS and throughput used for the robocopy job counts against your file share limits.
5351

54-
1. After the initial run completes, disconnect your application from the existing share and run the same robocopy command again. This will copy over all the changes that happened since the initial run, skipping any file data that has already copied over.
52+
4. After the initial run completes, disconnect your application from the existing share and run the same robocopy command again to copy over all the changes that happened since the initial run. Any data that has not changed since the last copy job will be skipped.
5553

56-
1. After the command completes for the second time, you can redirect your application to the new share.
54+
5. You can repeat step for as many times as you would like before cutting over to the new file share.
5755

5856
## See also
5957

0 commit comments

Comments
 (0)