Skip to content

Commit 63f7b56

Browse files
authored
Update storage-files-migration-linux-hybrid.md
1 parent 052a088 commit 63f7b56

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/storage/files/storage-files-migration-linux-hybrid.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ If you're not running Samba on your Linux server and rather want to migrate fold
3232
## Phase 2: Provision a suitable Windows Server instance on-premises
3333

3434
* Create a Windows Server 2019 instance as a virtual machine or physical server. Windows Server 2012 R2 is the minimum requirement. A Windows Server failover cluster is also supported.
35-
* Provision or add DAS. Network attached storage (NAS) is not supported.
35+
* Provision or add direct attached storage (DAS). Network attached storage (NAS) is not supported.
3636

3737
The amount of storage that you provision can be smaller than what you're currently using on your Linux Samba server, if you use the Azure File Sync [cloud tiering](storage-sync-cloud-tiering.md) feature. However, when you copy your files from the larger Linux Samba server space to the smaller Windows Server volume in a later phase, you'll need to work in batches:
3838

@@ -63,7 +63,7 @@ In this phase, consult the mapping table from Phase 1 and use it to provision th
6363

6464
[!INCLUDE [storage-files-migration-deploy-afs-agent](../../../includes/storage-files-migration-deploy-azure-file-sync-agent.md)]
6565

66-
## Phase 6: Configure Azure File Sync on Windows Server
66+
## Phase 6: Configure Azure File Sync on the Windows Server deployment
6767

6868
Your registered on-premises Windows Server instance must be ready and connected to the internet for this process.
6969

0 commit comments

Comments
 (0)