DFS - Namespace & Referal status
Hi,
I have the following question I've created a DFS name space \\domain.com\DFS\
I've created a shared folder on dc01 and dc02
public target folder
dc01\public - target folder
dc02\public - target folder
My understanding is that when a user types \\domain.com\DFS\public users will either go to \\dc01\public or \\dc02\public (whatever server responds first, generally based on AD sites)
So far this is what I've seen during my testing, however I want my users to always go to \\dc01\public and not to \\dc02\public so enabled one and disabled the other.
dc01\public - target folder - ENABLED
dc02\public - target folder - DISABLED
I am confused with the results because with \\dc02\public - target folder - DISABLED I am still getting my test users referred to \\dc02\public
My goal is to leave one enabled and one disabled so that users are only referred to one of the two servers/shares while the other one is disabled. Then when needed I would like to switch the enabled/disabled and change the referral to the other server so users go to it when they hit the dfs namespace.
Am I doing something wrong? Missing something
DFS.png
I have the following question I've created a DFS name space \\domain.com\DFS\
I've created a shared folder on dc01 and dc02
public target folder
dc01\public - target folder
dc02\public - target folder
My understanding is that when a user types \\domain.com\DFS\public users will either go to \\dc01\public or \\dc02\public (whatever server responds first, generally based on AD sites)
So far this is what I've seen during my testing, however I want my users to always go to \\dc01\public and not to \\dc02\public so enabled one and disabled the other.
dc01\public - target folder - ENABLED
dc02\public - target folder - DISABLED
I am confused with the results because with \\dc02\public - target folder - DISABLED I am still getting my test users referred to \\dc02\public
My goal is to leave one enabled and one disabled so that users are only referred to one of the two servers/shares while the other one is disabled. Then when needed I would like to switch the enabled/disabled and change the referral to the other server so users go to it when they hit the dfs namespace.
Am I doing something wrong? Missing something
DFS.png
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
you need to wait until referral period gets time out, you can change default value on folder target properties
you can reboot the clients, but its not best practice to reboot client for only to connect to new target
Better way:
No need to disable targets if you are setting the priorities as mentioned earlier, also then no need to do ad replication etc
you can reboot the clients, but its not best practice to reboot client for only to connect to new target
Better way:
No need to disable targets if you are setting the priorities as mentioned earlier, also then no need to do ad replication etc
ASKER
For the time being the DFS servers are in the same site. Is that going to work ok if we change the order?
Both NAS CIFS are in the same site right now, however on will be moved two q DR site later. We do not want the clients to go to the second NAS/CIFS shares unless we manually decide that in case of a DR case or scheduled failover. Is still save to go with priorities? How are the clients deciding where to go when you are using priorities? Any way to prevent the clients to get referenced to the DR with priorities?
Both NAS CIFS are in the same site right now, however on will be moved two q DR site later. We do not want the clients to go to the second NAS/CIFS shares unless we manually decide that in case of a DR case or scheduled failover. Is still save to go with priorities? How are the clients deciding where to go when you are using priorities? Any way to prevent the clients to get referenced to the DR with priorities?
yes, priorities are there for DFS servers in same site (AD Site) to refer only one target at maximum priority and failback to other target if 1st become unavailable
The DFS works based on AD sites and should not have any issues as long as sites to subnet assignment is correct
Before you move DFS server to DR location, you need to ensure that you do have one DC in DR location and eventually there would be one AD site for DR DC
Whenever client tries to access DFS targets, preference is given to DFS servers in local AD site, if it is unavailable, they will try to contact folder target in other site (DR) site.
For local AD site having multiple DFS servers, you could go with priorities,
In case of DR, you can keep DFS folder targets disabled because it should be activated only when you need to invoke DR
The DFS works based on AD sites and should not have any issues as long as sites to subnet assignment is correct
Before you move DFS server to DR location, you need to ensure that you do have one DC in DR location and eventually there would be one AD site for DR DC
Whenever client tries to access DFS targets, preference is given to DFS servers in local AD site, if it is unavailable, they will try to contact folder target in other site (DR) site.
For local AD site having multiple DFS servers, you could go with priorities,
In case of DR, you can keep DFS folder targets disabled because it should be activated only when you need to invoke DR
ASKER
Great. Looking to test this tomorrow. Would like to ask you one more thing...I can't used DFS-r since the data its going to be on CIFS shares not directly attached to the DFS servers but instead accessed via SMB. The vnxe Emc doesn't have a native way to replicate file level. I was wondering if you are aware of good tools to replicate file (byte level replication) I have looked at double take and peer sync but they are very expensive. Others like robocoy are not byte level aware.
Robocopy can't replicate open files, the files must be closed before you replicate with robocopy, it supports (by default) replication on incremental basis, if you try to replicate outlook PST files, those PST files can't be replicated while in use, after closure robocopy will replicate entire file I believe because it don't have any other option, in short try to avoid bulky files which have big size and changed frequently.
Storage is not my strong area
U can check with EMC, they must be having something like Snap-Mirror (NetApp) to replicate data across two locations
Storage is not my strong area
U can check with EMC, they must be having something like Snap-Mirror (NetApp) to replicate data across two locations
ASKER
Yeah...I am aware of that, unfortunately with the EMC VNXe 3200 there is no way to do file replication from within the array. So I am looking for software solutions to be able to get this done that will support bye level replication. So far I haven't found one that's good and not extremely expensive.
I am correct saying that you can't use DFS-R to replicate from external CIFS shares?
I am correct saying that you can't use DFS-R to replicate from external CIFS shares?
ASKER
You've mentioned that in case of DR, you can keep DFS folder targets disabled because it should be activated only when you need to invoke DR.
What needs to happen after the DR ones are enabled in order for the clients to switch from the previous ones to the new ones as fast as possible? I am trying to understand the procedure that I need to test and document in order to get this implemented.
What needs to happen after the DR ones are enabled in order for the clients to switch from the previous ones to the new ones as fast as possible? I am trying to understand the procedure that I need to test and document in order to get this implemented.
ASKER
What I meant to ask is from the admin side what do I need to do? My understanding is that any DC can give out referrals. Dfs based changes are always processed on the pdc. Root servers by default contact the pdc to get dfs based info. So what do we do do get the clients to referred to the new location?
yes, you can't use DFS-R for external shares
If your only DFS server gone down in primary site, AD will try to contact other DFS folder target and if target is enabled and changes are replicated to AD, it will be made available to users once their failed target referral is timed out
If total primary site is down including WAN links and servers, then I don't see any use of DFS DR apart from data storage. In that case clients will not be able to use DR DFS
If you have still client connectivity with DR, provided that DR DC is there, clients will get referred to DR DFS server
If your only DFS server gone down in primary site, AD will try to contact other DFS folder target and if target is enabled and changes are replicated to AD, it will be made available to users once their failed target referral is timed out
If total primary site is down including WAN links and servers, then I don't see any use of DFS DR apart from data storage. In that case clients will not be able to use DR DFS
If you have still client connectivity with DR, provided that DR DC is there, clients will get referred to DR DFS server
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
Thanks for your answer. Everything is going to be on the site site. So if we disable one target and later want to switch them I will have to force replication then wait at least 30 seconds for the clients to see the change? Would rebooting the clients help to find the new target?