File Server Migration (Share by Share) - Maintaining the UNC Namespace Using DFS

This video demonstrates how to use CopyRight2 to migrate a file server, share by share, while maintaining the UNC namespace using a DFS (Distributed File Services) server.

In this example, there is an old Windows® 2008 R2 file server called "WIN2K8R2FS" and a new Windows® 2012 R2 file server called "WIN2K12R2FS". The old Windows® 2008 R2 server has two file shares, called "Data1$" and "Data2$". In the video you can see how the "Data1$" share is migrated to the target, while maintaining access to both shares using the original UNC path "\\WIN2K8R2FS\Data1$" and "\\WIN2K8R2FS\Data2$" is maintained at all times during the migration.

Migrating share-by-share is a possible solution, besides of other methods, like the realtime synchronization, if there is a lot of data to migrate while having only a short timeframe to perform the migration, at the expense of a higher complexity.

The first step in this migration is to set-up a DFS server on the target system. You can see how to install it, in the first segment of the video. The DFS server could be installed onto a 3rd computer as well.

The next step is to migrate the existing file shares of the source server onto the DFS server. The so-called referral path is, in this example, the original file server's name with an appended "-RT" for retired.

Once this step is completed, the source server's computer name gets the name "WIN2K8R2FS-RT" and is rebooted.

Next some changes are made to the registry of the DFS server to give it the source server's original NetBIOS and fully qualified DNS names as additional names. After this step, users can access all the file shares using the original server name through the DFS server.

Finally a copy job is run, to migrate "Data1$" to the target server. CopyRight2 will automatically update the DFS referral path for "Data1$" to the new location on the target server, once the share is successfully migrated. After the share is migrated, users can still access "Data1$" by using the UNC path "\\WIN2K8R2FS\Data1$", but now residing on the new server. They can also access the "Data2$" share, still residing on the 2008 server.

So, instead of having to migrate an entire server and all the shares, the migration can be split into smaller segments doing one share at a time.