Site
No Namespace just replication
Server A > W2k3R2 Ent x64
Server B > Windows Storage Server 2003 SP2
Server C > Server 2k8 R2 Ent
We do not have full replication in place yet. Just Server A to B (local) and then B to C (DR Site)
I had a Server C that died so I built Server C to replace it. I went to add Replication and did not add the local path correctly. I left it the root of D: ... Now all the data starting copying over to Server C D:\root so I disabled it knowing of my mistake. All I wan to do do is have the data start going to the NEW local path on the new server I will create. I'm afraid if I leave B to C disabled and create the new "membership path" ... once created the data still trying to go to root of c will take off and the new local path will populate too? I'll try to show what I want to do to see of it makes sense.
Leave Connection to B to C disabled.
Go under root of C Server (D:\ and delete what as copied over so far)
Delete Membership in Replication for the C server and recreate new membership to correct location.
Turn on Replication from B to C with new location so replication starts.
Not sure if this will work since we have that 60 day "tombstone" setting from DFS. I'm afraid that even though I deleted the data from Server C that when replication is stated back up it may in some way try to go back to Server B ?? Again I have replication one way B to C.
Make any sense?