File Server Migration from 2012 to 2022

Hello lmgmcg,

I wanted to quickly follow up on your DFS migration to ensure the replication groups are syncing correctly on DC02. As discussed, please exercise caution when increasing the staging quotas; applying a blanket 100GB limit per replicated folder can rapidly exhaust the physical disk space on the target volume if it is not sized to handle the cumulative reservation of all staging folders combined (e.g., 5 folders x 100GB staging = 500GB reserved space). The most stable and efficient configuration is to size each specific folder's quota slightly above the sum of its 32 largest files using the PowerShell method provided earlier. This prevents "staging space exceeded" backlogs during the initial sync without wasting valid storage capacity.

If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP

Hello lmgmcg,

Yes, you will be able to view and manage the exact same DFS structure from DC02. Because your namespace \\company.local\Data is a Domain-based namespace, the configuration metadata resides in Active Directory partitions, not in the local registry of the specific namespace server. This means that any domain controller or member server with the RSAT-DFS-Mgmt-Con tools installed can view the same topology once connected. However, when you first launch the DFS Management console on DC02, the console tree will likely be empty. You must explicitly right-click the "Namespaces" node, select Add Namespaces to Display, and query the domain to load your existing company.local\Data namespace into the view.

Your proposed workflow is technically sound, but there are two specific configurations you should verify during the replication setup for a dataset of that size. When you add the folder target and trigger the replication group creation wizard, ensure you adjust the Staging Quota for the new member. The default staging size is 4,096 MB (4 GB), which is often insufficient for an initial sync of 200 GB if the dataset contains large individual files (like Outlook archives or ISOs). A best practice is to set the Staging Quota to be slightly larger than the sum of the 32 largest files in the replicated folder; otherwise, replication may enter a "retry" loop and slow down significantly. Furthermore, when you are ready to retire DC01, ensure you remove DC01 from the Namespace Servers tab in the console before you demote the domain controller or shut it down. This ensures the Active Directory object for the namespace is cleanly updated to remove the referral to the old server.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Yes, you will be able to see the same DFS Management window on dc02 after you install the DFS Management tools. To do this, you need to install the DFS Namespaces and DFS Management Tools on your Windows Server 2022 (dc02). You can do this using Server Manager or PowerShell.

Installation Steps:

1. Using Server Manager:
   • Open Server Manager, click Manage, and then select Add Roles and Features.
   • Follow the wizard to install the DFS Namespaces role under File and Storage Services > File and ISCSI Services.
2. Using PowerShell:
   • Open an elevated PowerShell session and run the following command:

      Install-WindowsFeature -Name "FS-DFS-Namespace", "RSAT-DFS-Mgmt-Con"  
   

After installation, you should be able to access the DFS Management console on dc02, allowing you to manage the DFS setup, including disabling and deleting folder targets as needed during your migration process.

References:

• DFS Namespaces overview
• Install DFS Namespaces