Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1214
  • Last Modified:

DFS Server Redundacy

We have several servers hosting shares and one server with DFS which manages those shares into a single one.

Ex.
Server0
DFS Share "Shared" \\domain.com\shared
DFS targets
"Share1" on Server5
"Share2" on Server5
"Share3" on Server3
\\domain.com\shared\share3 <-- DFS Share
\\server3\share3\ <-- direct server share

The thing im worried about now is if Server1 goes down the one with DFS root "Shared"
the clients wont be able to access any of the target shares above even though those shares are up and running.

How do i make the shares redundant so that there is a identical DFS root on 2 or more servers pointing to the same shares, but no replication i dont want to copy any data just the links to those shares and if possible make it automated so i dont have to make the same share on each DFS server.

Ex.

DC1 Server0
DFS Share "Shared"  \\domain.com\shared
DFS targets
"Share1" on Server5
"Share2" on Server5
"Share3" on Server3

DC2 Server1
DFS Share "Shared" \\domain.com\shared
DFS targets
"Share1" on Server5
"Share2" on Server5
"Share3" on Server3

Note i have sites and services all configured so each client will go to \\domain.com\shared and it will be local DC on that site.
0
pboustani
Asked:
pboustani
  • 3
  • 2
1 Solution
 
LauraEHunterMVPCommented:
I don't understand the requirements you're outlining here: "How do i make the shares redundant so that there is a identical DFS root on 2 or more servers pointing to the same shares, but no replication i dont want to copy any data"

So you want to have a share called \\dfs\shared that exists on more than one server...but with the data only existing on one server?  What does that do for you if the server that is hosting the data goes offline?  The way that DFS provides redundancy is via replication - specify more than one DFS target for \\dfs\shared, and DFS will replicate the data between the various targets so that they stay loosely consistent with each other.
0
 
pboustaniAuthor Commented:
No no, i dont want same share on multiple servers. I want multiple DFS servers.
Ex.
These are my shares lets say each one on a different server on a different site.
Share1   \\server5\share1
Share2   \\server3\share2
Share3   \\server4\share2

DFS Server0
Target 1 - \\server5\share1
Target 2 - \\server3\share2
Target 3 - \\server4\share2

There are two ways of connecting to the shares.
PC -> Server (Directly to the server that they are located in - \\server5\share1)
or
PC -> DFS Server -> Server ( \\domain.com\DFSshare\target1)
My DFS server does not hold any data it just has basicalyl links to the shares, but its all in one central location and i map a drive to the DFS root \\domain.com\DFSshare
My problem is now if the DFS server goes down my clients cant connect to the shares because the link was broken (\\domain.com\DFSshare\target1) but the direct path still works (\\server5\share1)

The reason i dont want data replication is because my servers are in different sites and there is a lot of data which will kill my internet, its already maxed out by other stuff.

I just want a 2nd DFS root with same links that can be accessed if one of the roots(DFS servers) goes down. If the server with the share it self goes down then thats ok no one will be able to access that share but if the DFS server goes down no one can acess any shares unless i give them alternate paths.

I hope thats more clear

TIA Cheers.
0
 
pboustaniAuthor Commented:
Points increased to 250. I guess a simpler form of the question is:

How to I make DFS redundant so that if my PDC running DFS goes down, users will still be able to access the identical DFS shares because of a redundant DFS setup on one of my other DCs?

We heavily use DFS mainly for grouping shares from multiple servers into one convienent location.

Thanks.
0
 
LauraEHunterMVPCommented:
If your concern is simply allowing clients to continue to access configuration information of your DFS namespace - folder1 is on server1, folder2 is on server2, etc. - simply configure your DFS namespace as a domain-based namespace so that your DFS configuration is stored in Active Directory; clients will then be able to access DFS configuration information from any available domain controller.  

This solution, however, will not by itself allow clients to continue to access files on server1 if server1 becomes unavailable, for example. To allow your clients to continue to access file shares in the event that a DFS link target becomes unavailable, you will need to configure multiple physical link targets for the DFS folders in question and configure DFS replication between them. So if you have the \\company.com\sharedfiles\Finance DFS folder housed on \\server1\finance, and you want your clients to be able to access the Finance files even if server1 becomes unavailable, configure one or more additional link targets for \\company.com\sharedfiles\Finance, say \\server2\finance and \\server3\finance, and then allow DFS to replicate information between server1, server2, and server3.  

Configuring DFS replication is described in detail in the following tutorials:

http://www.windowsnetworking.com/articles_tutorials/Implementing-DFS-Replication.html
http://www.windowsnetworking.com/articles_tutorials/Configuring-Using-DFS-Replication.html
http://technet2.microsoft.com/windowsserver/en/library/5A22DC44-301D-425D-8A0F-2D32A1C44A7F1033.mspx
0
 
pboustaniAuthor Commented:
Thank you, that was perfect, exactly what i wanted.

Cheers.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now