Skip to content

Commit cdb2671

Browse files
Merge pull request #224755 from sindamnataraj/nasindam/migration-afs
Nasindam/migration afs
2 parents 132bfb4 + 809bad1 commit cdb2671

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ A scenario without a link doesn't yet have a published migration guide. Check th
7676
| Source | Target: </br>Hybrid deployment | Target: </br>Cloud-only deployment |
7777
|:---|:--|:--|
7878
| | Tool combination:| Tool combination: |
79-
| Windows Server 2012 R2 and later | <ul><li>[Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Azure File Sync and Azure DataBox](storage-files-migration-server-hybrid-databox.md)</li></ul> | <ul><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li><li>Via Azure File Sync</li></ul> |
79+
| Windows Server 2012 R2 and later | <ul><li>[Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Azure File Sync and Azure DataBox](storage-files-migration-server-hybrid-databox.md)</li></ul> | <ul><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li><li>via Azure File Sync: Follow same steps as [Azure File Sync hybrid deployment](../file-sync/file-sync-deployment-guide.md) and [decommission server endpoint](../file-sync/file-sync-server-endpoint-delete.md) at the end.</li></ul> |
8080
| Windows Server 2012 and earlier | <ul><li>Via DataBox and Azure File Sync to recent server OS</li><li>Via Storage Migration Service to recent server with Azure File Sync, then upload</li></ul> | <ul><li>Via Storage Migration Service to recent server with Azure File Sync</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
8181
| Network-attached storage (NAS) | <ul><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 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> |
8282
| Linux / Samba | <ul><li>[Azure File Sync and RoboCopy](storage-files-migration-linux-hybrid.md)</li></ul> | <ul><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |

articles/storage/solution-integration/validated-partners/data-management/migration-tools-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ The following comparison matrix shows basic functionality of different tools tha
9999
- Internal hash validation
100100

101101
> [!TIP]
102-
> Azure File Sync is meant as a permanent, hybrid solution for on-premises caching / sync of a number of Azure file shares. In that function, it provides zero-downtime cloud migration. If you do not plan on caching your Azure file shares on-premises, Azure File Sync is not a recommended migration tool. Refer to the [Azure file share migration overview](../../../files/storage-files-migration-overview.md) or the other partner tools described in this article.
102+
> Azure File Sync can be utilized for migrating data to Azure Files, even if you don't intend to use a hybrid solution for on-premises caching or syncing. This migration process is efficient and causes no downtime. To use Azure File Sync as a migration tool, [simply deploy it](../../../file-sync/file-sync-deployment-guide.md) and, after the migration is finished, [remove the server endpoint](../../../file-sync/file-sync-server-endpoint-delete.md).
103103
104104
### Datadobi DobiMigrate
105105

0 commit comments

Comments
 (0)