DFS - Shared Folder cleanup

Good Afternoon,

We have a single domain environment that is using DFS shares across multiple remote sites in a full mesh topology. We are in the process of cleaning up the main shared folder in order to better control permissions and ease of access. We will be moving a great deal of existing data under subfolders that have different ACLs

Before we move forward, we would like to check with others to make sure that this would not cause DFS replication errors across the sites.

Also, will the files have to be “re-copied” from one server to the next in order to put them in their locations or will it know to simply move them under the needed folders?

Thank you!
NMTSupportAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

MaheshArchitectCommented:
If dfs replication is already working fine across targets then:
When you move \ cut data from one location, it will be considered as deleted from that location and deletion gets replicated to all servers
Like wise when you paste data to new location, it will be considered as new data copy / addition and same will be replicated to other servers
0
kevinhsiehCommented:
Since all servers have all of the bits for the files, it should not cause issues. For example,  if you move a 1 GB file I would not expect a significant amount of WAN traffic due to replication. You can test just to be sure.

My DFS Replication is under the Enterprise feature set so it has cross file replication, so that may make a.difference, but I don't think it does in this case.
0
SteveCommented:
the work you have planned shouldn't cause errors as such, but doing too much too quickly could cause conflicts.

a few pointers to keep it all working OK:

Don't do to much at a time. allow a bit of time for changes to replicate before doing more.
Take care when moving files/folders between replication groups, as this will need the entire file to re-replicate.
Make changes on ONE server only. never do stuff on more than one or you'll end up with conflicts
check the size of your staging area. if this is too small your changes will get backlogged.

with regard to re-replicating when moving, DFS works on USN journals. As long as the files/folders move within the same replication group, and you move it (not copy) it should remain the same file. DFS will work this out accordingly and shouldn't have to replicate the entire file again unless it detects significant changes.
0

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
NMTSupportAuthor Commented:
Thank you very much for the pointers and the advice!
0
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 2008

From novice to tech pro — start learning today.