I can't see you getting much of and answer the way you have phrased this
question. First, why is the namespace an issue? DFS will use
\\Domain.com\DFSRoot (or \\DFSServer.Domain.com\DFSRoot)
Your issues in changing the name space from UNC to DFS are similar to those of
renaming a server, all the clients must change. However with DFS once you have
changed it becomes much easier to switch between servers by simply changing the
DFS structures. In addition you can start to use DFSR (replication) for
redundancy
On Fri, 16 Apr 2010 20:36:44 +0100, Andrew Hodgson <>
wrote:
>Hi,
>
>I currently have a file server running W2k3 R2 with around 1.2 TB of
>data. I have moved up through file servers before, and usually copy
>everything to the new machine, then rename it the same as the old
>machine.
>
>The new box I want to move the data to runs Windows 2008 R2, and I was
>thinking about using DFS.
>
>The issue I have is the namespace I want to keep is server.domain.com,
>and I can't implement that namespace as the old server is currently
>using it for ordinary shares.
>
>At present I only have one server, though may introduce more machines.
>I have a DR site, but only copy a subset of data to the server DR
>site, so replication may be an issue. Is it worth doing?
>
>Thanks.
>Andrew.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|