Storage migration 2008 R2 - DFSR DB implications

hello,

i have storage migration requires dfsr changes.  unsure of how these changes affect dfsr db , thoughts.  it’s bit complicated , hope makes sense.  this applies win 2008 r2 sp1.

here scenario.  we have multiple fileservers around 1500 users @ 1 location.  these servers store user h drive data , replicate dfs replica server in our dr site.

the 4 host (live) site servers users , broken down last name.

server1:  usersa-f

server2 : usersg-l

server3:  usersm-r

server4:  userss-z

there 2 replica site servers.  so shares usersa-f , usersg-l replicate single server separate drives each.

the issue host site drives full. have new san mounted drives , plan split off data such.

server1: d:\usersa-f becomes d:\usersa-c , k:\usersd-f.  server2: f:\usersg-l becomes f:\usersg-i , l:\usersj-l

the replica site has 2 new drives , store 4 drives of replicated data.  usersa-c, usersd-f.  usersg-i, usersj-l.

i focus on 1 server – usersa-f on server1.  have plenty of experience robocopy preseed , checking hashes.

here high level steps:

1. copy data new drives using robocopy preseed command (host , replica side)
2. check file hashes
3. re-sync needed (using robocopy /xo switch)
4. share new root folders (on new drives)
5. delete existing replication group(s)
6. un-share, re-name, re-share existing root shares – usersa-f renamed usersa-c
7. configure new dfs links/targets etc
8. create new replication groups(s)
9. once replication happy delete un-needed (redundant data) each drive

-          delete d-f data existing drive holds a-c data

-          delete a-c data new drive holds d-f data

the part i’m unsure #6 - un-share, re-name, re-share existing root shares. 

the existing share usersa-f.  i have re-name share usersa-c means have un-share first.  then re-name, , re-share.  i have similar work on replica side.  i’m worried how affect existing dfsr database?  when create new replication group, initial sync (check file hashes) normal , catch on replication or confused since root has been un-shared , re-named?  the dfsr database see new replicated folders (a-f replaced a-c , d-f).  will re-replicate over?  that big worry.

thank you!

 

 

hi, 

since have deleted existing replication group @ step 5, step6 not affect existing dfsr database. 

when create new replication group, initial sync between shares usersa-c on server1 , new san mounted drive on replica site server.

after step 9, think 2 replication groups needed between server1 , replica site server replication shares usersa-c , shares usersd-f. set replica site server primary member in replication group. considered authoritative member , wins out during initial replication. overwrite current replicated folder content on non-primary member. 

try command set server primary:

dfsradmin membership set /rgname:<rg name> /rfname:<rf name> /memname:<member name> /isprimary:true

best regards,

mandy

---

we trying better understand customer views on social support experience, participation in interview project appreciated if have time.
helping make community forums great place.

Windows Server  >  File Services and Storage