Jump to content

Recommended Posts

Posted

Hi,

 

I am setting up DFS for our home areas. Back in the 2003 days this was a pain, these days things seem to be much better! I have tested this out. But i have a few questions for people who have experience with this. I want to make sure i get this bang on.

 

I have already setup a namespce, had this for years. Its so if i move about file servers the path doesn't change. Anyway i want to replicate the files in this area. Do i setup the replication let it replicate over the weekend and then add it to the name space? Or shall i add it to the name space the same time as i setup replication? I have quotas on the home areas. I believe i have to set them up on both servers, so i assume the first option is the best.

 

Also what do you fellas have setup for your Staging Area Quota?

 

Thanks

Posted

Setup replication - let it tick over (it will take quite some time and don't feel tempted to restart either target or source server until its done) and then add to namespace.

 

Everything is seamless from there on in :)

 

For staging area when doing the initial sync set it quite high (up to a few 100GB has worked well for me in the past) and then gradually reduce over time once its back into action (mine usually sits at 30GB).

  • Thanks 1
Posted
Yeah don't get tempted to set the staging area too small, mine is 16GB between my two 1.5TB file servers (too small still I think). You'll get errors popping up in event viewer if it's too small, and performance will suffer.
  • Thanks 1
Posted

It's still been strongly advised not to use replication for home areas. Has something changed recently making that less of an issue?

I'd still quite like to use it (again, I hasten to add after initial problems) to counteract our split-site setup and the possibility of issues at either site but the aforementioned advise goes against it.

Posted
Not seen that advice myself - what do you think would be the reasoning for it? Perhaps it's due to the number of files opened and locked for a long time if AppData is redirected, which DFS-R will moan about.
Posted

As for monitoring you can also run a health report from the DFS console to see backlogged files etc.

 

What version are the boxes? there's major improvements in newer versions of DFSR, but if using mixed versions you're pushed down to the lowest common DFSR version.

 

The home areas thing I would imagine due to DFSR not replicating file locks. As long as your users aren't on multiple machines at once across sites I would have thought you'd be okay?

Posted
As for monitoring you can also run a health report from the DFS console to see backlogged files etc.

 

What version are the boxes? there's major improvements in newer versions of DFSR, but if using mixed versions you're pushed down to the lowest common DFSR version.

 

The home areas thing I would imagine due to DFSR not replicating file locks. As long as your users aren't on multiple machines at once across sites I would have thought you'd be okay?

 

One box is Server 2012 and the other is Server 2012 R2.

 

Thanks

Posted

Right, I have got replication working well (test share). Works fine. I can see 2 servers in the namespace server in the DFS management console. When I turn off the original server I replicated from, I can't get to the share, (I am using the namespace address).

 

Anyone got any ideas please?

 

Thanks

Posted
Is 'enable referrals for this folder target' selected on the new namespace member? Has replication finished between the two?

 

Yep the button is ticked and replication has finished.

 

Thanks

Posted

Anyone got any ideas please?

 

Thanks

 

Is this from an authenticated client, or a local account? Reason I ask is my work PC account is a local, non-domain account, so when I access my namespace I have to authenticate with my network credentials. Being DFS, it may then ask me to authenticate again at any point while browsing the shares as it decides to swap server, until I'm auth'd on both servers. These can occasionally play up, leaving me locked out and I have to reset the authentication by logging off and back on.

 

If I log in with a network account, I don't get this behaviour. Have you tested it on a network account?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...