Jump to content

Recommended Posts

Posted

We have a win 2008 R2 DC. It was our only server.

I was concerned about if this server goes down! So....

I've added an extra 2008 R2 server. It has AD roles and File Services role, including replication and namespace roles.

 

I've managed to setup a namespace and setup a folder working under replication. It was a mapped drive, so I changed the GPO where this is set so that it uses the namespace address instead. All seems to be working, and the files replicated ok.

 

However, this was quite a length process, and took a while to setup just for 1 folder.

 

I have lots of folders I need to do replication for and alter the GPOs so that they use the namespace address as opposed to the individual server address.

 

Are there any ways to speed this process up? If it helps, on the PDC Server, there is an E drive with lots of folders which contain the different shares (e.g. studenthome, staffhome, public, tech). I would like each of these to be replicated, and to come under the namespace address.

 

Apologies in advance for incorrect terminolgy- I am learning as I go. Thanks.

Posted

Not really. Every time I've tried to do something which theroretically speed it up it has ended up with me starting again. Just letting it get on with it has left me with a completely stable and reliable replica although it took about a week to replicate the 4TB or so it was then.

 

The only thing I would say is to make sure your staging quota is sufficient. Mine is roughly 60GB

  • Thanks 1
Posted

THanks for your help Sagima. Is there any way to speed up setting permissions? When I am setting the replication folder in the DFS console on DC01 for DC02 (creating a new shared folder), I then have to set the permissions again on that folder.

 

ALso, does the staging quota need to be at least as big as the biggest file to be replicated for that share? Default is 4GB, but the drives are only 1TB (small primary). If I set staging too high, presumably it will eat up a lot of space, especially when there are multiple folders to be replicated.

Posted

It's actually supposed to be the size of the 32 largest files on your file server (and mine isn't even that it's the size of the 2 largest - which were .wim files). It sticks copies of the files currently being replicated in the hidden System Volume information folder (which from now on will be much larger).

 

NTFS permissions get migrated but shares don't - is that what you mean when you say you have to set the permission again?

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...