Skip to content

Commit 3a014ad

Browse files
committed
fix links
1 parent a5d8749 commit 3a014ad

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/storage/files/storage-files-migration-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ File fidelity in a migration can be defined as the ability to:
5252
- Transfer files with the migration tool.
5353
- Store files in the target storage of the migration. </br> The target for migration guides in this article is one or more Azure file shares. Consider this [list of features that SMB Azure file shares don't support](files-smb-protocol.md#limitations).
5454

55-
To ensure your migration proceeds smoothly, identify [the best copy tool for your needs](#migration-toolbox) and match a storage target to your source.
55+
To ensure your migration proceeds smoothly, identify [the best copy tool for your needs](#migration-guides) and match a storage target to your source.
5656

5757
> [!IMPORTANT]
5858
> If you're migrating on-premises file servers to Azure Files, set the ACLs for the root directory of the file share **before** copying a large number of files, as changes to permissions for root ACLs can take a long time to propagate if done after a large file migration.
@@ -163,7 +163,7 @@ A scenario without a link doesn't yet have a published migration guide. Check th
163163
| Linux (SMB) | <ul><li>NA</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li></ul> |
164164
| Network-attached storage (NAS) | <ul><li>Via [Storage Mover upload](migrate-files-storage-mover.md) + [Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Via Azure File Sync upload](storage-files-migration-nas-hybrid.md)</li><li>[Via DataBox + Azure File Sync](storage-files-migration-nas-hybrid-databox.md)</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>[Via DataBox](storage-files-migration-nas-cloud-databox.md)</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
165165

166-
### File-copy tools
166+
### Select a file-copy tool
167167

168168
To select the right tool for your migration scenario, consider these fundamental questions:
169169

articles/storage/files/storage-files-migration-robocopy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ An example: *RoboCopy /MIR* will mirror source to target - that means added, cha
4444
Before you can use RoboCopy, you need to make the Azure file share accessible over SMB. The easiest way is to mount the share as a local network drive to the Windows Server you're planning on using for RoboCopy.
4545

4646
> [!IMPORTANT]
47-
> Make sure you mount the Azure file share using the storage account access key. Don't use a domain identity. Before you can successfully mount an Azure file share to a local Windows Server, you need to have completed [Phase 2: Preparing to use Azure file shares](#phase-2-preparing-to-use-azure-file-shares).
47+
> Mount the Azure file share using the storage account access key. Don't use a domain identity.
4848
4949
Once you're ready, review [Use an Azure file share with Windows](storage-how-to-use-files-windows.md). Then mount the Azure file share you want to start the RoboCopy for.
5050

0 commit comments

Comments
 (0)