DFS: Move local share to another disk

I have two W2003 R2 servers connected with DFS via a 1 Mb/s WAN. This works great.

However, one server is running out of space, and I need to move the local share to another drive.
What is the best method to do this without starting a major replication?

I tried to xcopy the full share with all user rights to the new drive and attach that as new share with another drive letter. Problem is that the DfsrPrivate folder is copied as well, and I think that confuses DFS. But what else to do? Can I simply delete the DfsrPrivate from the new share before attaching it?
Or should I make the copy to the new drive, remove the old drive, mount the new, and assign it the old drive letter? Both drives contains one partition only and will have identical folder structure.

LVL 55
Gustav BrockCIOAsked:
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.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
Don't delete DfsrPrivate, as this will delete the replication group.

Perform the migration as follow

1. Robocopy --- /sec /e /b /v seems enough.

2. Remove the folder target in DFS management, the old share and the replication group --- you could recreate the group easily after creating the namespace.

3. Share the new folder, add to DFS-namespace. It should ask for creating a replication group. If not, right click on the folder under namespace and choose Replicate Folder.

For more information check the links below



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
Gustav BrockCIOAuthor Commented:
Thanks. I had Robocopy in mind but recalled some issues with W2003 (as mentioned in the second link of yours) but perhaps those are solved by now? That's why I used Xcopy which is a bit slow but does the job of copying the user permissions.

Also, your method seems valid to me, but why does the second link of yours mention "pre-seed" without explaning what is does, neither why it should be needed?
If it is needed, the link states that NTBackup must be used. But how? NTBackup doesn't make sense to me in this context.

At the bottom of your first link, "Server Engineer" has written a guide. This neither doesn't mention "pre-seed".
His method for exchanging the share is a bit different from yours. Could your please briefly describe to pros and cons for the two methods?

Gustav BrockCIOAuthor Commented:
Except that I used Xcopy and skipped the pre-seeding mention in the link, I managed to get it up and running.
Effectively, as you state, you remove the old path and add the new. It's not difficult; the problem is that you don't do this very often so you may not be familiar with the steps, but for important data as in this case, you have to follow a safe route.

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
Microsoft Server OS

From novice to tech pro — start learning today.