Post by DaSaint
Win 2003 R2 Domain
Server1\DFSRoot(folder)\DFShareA replicates to
Server2\DFSRoot(folder)\DFShareB replicates to
Do you mean that all your data is physically in the DFSShareA folder, i.e. you
has created a DFS Share and instead of creating links to other shared folders
you have actually copied the data to the DFSRoot folders. If so this is a very
bad idea. The design concept is that the DFSRoot will contain only "Links" that
point to shares (which may be on the same server as the DFSRoot). If you read
"How DFS Works" (http://technet.microsoft.com/en-us/library/cc782417.aspx) you
will find all the limitations on the number of folders supported in the DFSRoot.
If the data is stored in a linked shared folder then you should be able to
simply enable/disable the links to switch users between servers.
Share the data folders as \\serverA\Data$ and \\ServerB\Data$
Users can access data via ether share (avoiding DFS) so hide the shares by
Set up a DFSR replication between the two above shares.
Create a DFSRoot folder: \\domain.com\DFSRoot
Add a folder in the DFSRoot called "Data" and link it to the two above shares.
Users will now be able to access the data using the DFS path \\domain.com\data.
They will either be redirected to \\serrverA\Data$ or to \\serverB\Data$.
You then disable the link to ServerB and the users can only be directed to
\\ServerA\Data$. When you wish to switch the users simple disable the link to
\\ServerA\Data$ and enable the link to \\ServerB\Data$. Wait for all client to
switch over (takes up to 1800 seconds by default). Note that older XP and W2K
will never do this switch without a reboot.
As to one way replication. You are assuming that the users will not try to
change the data when you have the using ServerB. You would need to set the share
permission on \\ServerB\Data$ to ensure this is the case. Users will not do this
reliable otherwise. But why stop them? They can continue to access the data on
serverB updating it as needed. When you eventually switch them back to ServerA
the data will be up to date if you had two way replication in place.
Watch out for Quotas though as two way replication can run into serious problems
if quotas are in use.
Post by DaSaint
Only the source share is available to the end-user; we are a single AD site,
multiple locations. The intent was that if Server1 went down, we could
manually changeover to Server2 with minimal effort.
So now we have a DR test scheduled, and we're scratching our heads saying
"How do we do this?"
We want to take down Server1 and have staff connect to DFShareA on Server2.
They would not be changing any data for the test, so the one-way replication
should be OK(?)
If I create a second namespace to Server2\DFSRoot(folder)\DFShareA, will it
alter the contents/permissions of the files there? Will it then be
potentially used for production work after the test?
There are 10 types of people, those that understand binary and those that don't.