Hi globetrotter,
Thanks for the information. Just to clarify (in case you need it to add anything), I'm looking at scenario one. I need the second one to be available to clients, but only if the colo (or the connection to the colo) fails.
Now even though the two buildings are in different subnets, I was wondering if I even needed to put them into different AD sites - one, since the colo will only contain servers, and two, since we're running at extremely high speeds. Am I off base?
Also, my current file server (which I haven't moved) is a 2003 R2 box. I'm curious if there are any benefits of having the colo file server, as well as the DR server, run 2008 64-bit. Does 2008 offer any improvements in the DFS realm? I hear going 64-bit will help with large data sets (which mine are), but that could be marketing fluff.
Thanks again,
Ryan
Main Topics
Browse All Topics





by: globetrotterPosted on 2009-02-26 at 21:35:39ID: 23752981
Hi,
Do you want your clients to primarily use the first server, but fall back to the other one if the first one is not available (1), or do you just want to have the second one as a backup that never gets accessed by the clients?
(1) For this you can define Target Priority. If the 2 Subnets that you mention are assigned to 2 different sites in AD you would need to set global high (or in the R2 Console - First among all targets) if they are in the same site, you can use Sitecost high (first among targets with equal cost).
(2) For DFS Links you also have the possibility to disable the referrals. In this case the server remains part of the DFS Structure, but the clients will never find out about it. This can be done only for Link Targets. In the (pre-R2) DFS Console right-click the link target and choose disable.