SOLVED

Windows File Server migration

Copper Contributor

Hi All,

 

We are migrating windows file shares to azure file. and we have requirement : for user it will smooth transition e.g they will acccess same folder path even after migration to azure files

 

Factor consider for contribution

stg ad domain

Files Sync

DFS

 

Please help if any one already worked

 

4 Replies
best response confirmed by santosh150 (Copper Contributor)
Solution
Hi, Santosh, involves careful planning and execution!
I think some key factors and steps to consider ensuring a seamless migration experience:
1. Preparation and Assessment
Evaluate Current Environment: Assess the size, permissions, and types of data on your current file shares. Tools like the Storage Migration Service can help in assessing the environment.
Plan for Azure File Shares: Decide on the performance tier based on your needs (Premium, Standard, etc.). Also, estimate the cost based on the size and access patterns.
2. Integration with Active Directory (AD) Domain Services
Care of the Azure AD DS Authentication and DNS Configuration etc.
4. Implement File Sync and DFS
Set up Azure File Sync to sync your on-premises file server with Azure File share. This will replicate data and can also be used to tier cold data to Azure while keeping frequently accessed data on-premises.
Use Distributed File System (DFS) Namespaces to maintain the same folder paths for users. DFS can abstract the file share's physical location, allowing you to change the backend without affecting user access paths.
Agreed, Azure file with Azure file sync is a good method to consider including synchronization of the permission of the shared folders
Hi Juhua,
Wanted to check with you about an environment with shared folder synchronized with Azure with Azure File Sync with local DFC namespace implemented.
- Azure File integrated with AD DS
- Azure Entra ID connector connected

If the HQ completely down due to disaster, users need to access the Azure File directly with Point-to-Site VPN, can we still have DFS service in Azure (if possible) to resolved the namespace ? (HQ down, local DFS server also down)

Would like to know whether there's any best practices available to meet this DR requirement?

Regards,
Kho

1 best response

Accepted Solutions
best response confirmed by santosh150 (Copper Contributor)
Solution
Hi, Santosh, involves careful planning and execution!
I think some key factors and steps to consider ensuring a seamless migration experience:
1. Preparation and Assessment
Evaluate Current Environment: Assess the size, permissions, and types of data on your current file shares. Tools like the Storage Migration Service can help in assessing the environment.
Plan for Azure File Shares: Decide on the performance tier based on your needs (Premium, Standard, etc.). Also, estimate the cost based on the size and access patterns.
2. Integration with Active Directory (AD) Domain Services
Care of the Azure AD DS Authentication and DNS Configuration etc.
4. Implement File Sync and DFS
Set up Azure File Sync to sync your on-premises file server with Azure File share. This will replicate data and can also be used to tier cold data to Azure while keeping frequently accessed data on-premises.
Use Distributed File System (DFS) Namespaces to maintain the same folder paths for users. DFS can abstract the file share's physical location, allowing you to change the backend without affecting user access paths.

View solution in original post