Move DFS-R Replication Groups to a new Server?

Hi, I need to move my DFS-R replication groups/folders from one server to another. Right now they are hosted on Server1 with a SAN that is quickly running out of space. I need to move them to Server 2 which has a SAN with plenty of space to grow. Is there a way to do this without starting over, or causing DFS-R to do it's initial replication again?

I am not using namespaces.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Yes, go into the dfs management interface, under the replication group, add the new server as the target and there you can specify the drive letter and the directories where you want the data. Let the data replicate, then when the replication completes, you can add the new servers as the dfs target. Give it time, and then remove the old server from the dfs share target. At this point you can remove the old server from the replication group.

When configuring replication make sure you use mesh and not a hub spoke if you want changes at either to replicate to the other.

The transition will require the users to reconnect to the new server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rex-PrinceAuthor Commented:
Sorry Arnold, I have not had a chance to try this out. I will hopefully be able to by the end of the week.

Can I seed this new member, or do you recommend that I let it replicate to an empty directory?
it is up to you.  If you use xcopy/robocopy to preserve ownership and ACL rules, you can move it at will.  The benefit of letting it replicate is, that should some clients still have a connection to the current server and update a file, it will replicate to the new one when the file is closed.  If you copy and retarget, you might miss this file update since the copy will not work on an open file.

Yes, let data replicate to a new/empty folder on the new system.
you can test replication by creating a new test file on the new server after replication is setup to make sure the file makes its way to the current server.
Get a highly available system for cyber protection

The Acronis SDI Appliance is a new plug-n-play solution with pre-configured Acronis Software-Defined Infrastructure software that gives service providers and enterprises ready access to a fault-tolerant system, which combines universal storage and high-performance virtualization.

If you want to pre-seed, here is the definitive post from Microsoft on how to do that.

Replacing DFSR Member Hardware or OS (Part 2: Pre-seeding)
I suggest that now is the time to start using namespaces, since you will have to reconfigure all of your clients anyway, you might as well do it for the last time.
Rex-PrinceAuthor Commented:
I did a test run with one replication group. I used robocopy to preseed and it seems like I had a lot of conflicts on the initial replication. I used these parameteres: robocopy "source" "destination" /mir /sec /s /e /r:1 /w:0

Is there a different switch, maybe COPYALL would be better?
No, if using dfs-r there is no need to preseed given when a replication partner is added it is seen as empty whether it is or not.
If you read the link I provided, you do require /COPYALL in order to properly pre-stage the content, and you need to use the correct version of Robocopy.

3. Sync the folders using robocopy with the following argument format:

Robocopy.exe “\\source server\drive$\folder path” “destination drive\folder path” /b /e /copyall /r:6 /xd dfsrprivate /log:robo.log /tee
Rex-PrinceAuthor Commented:
One last question. I added the new Member, and now I have three Servers in this Replication group. The Current Server (Server1/SAN), the Current Replication Server (Server2), and the New Server (Server/SAN).

Server1 is the Primary in that group, and that is the Server I plan on removing when this over. Is there a way to switch the Primary role, or is that just for initial replication?
The primary is only for initial replication. Once replication has happened, there is no such thing as a primary server. When you are done and you want to remove the original server, just remove it from the replication group.
You should first remove the server from the share section. Once no clients use the share on this server, remove it from the replication group.
Rex-PrinceAuthor Commented:
Thanks Arnold. I did exactly what you said and it worked like a champ. Kevin, thanks for the info on pre-seeding. I will use that for new replication groups.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.