We have two AD integrated DCs one of which (ServerA, the PDC emulator) also acts as file server, handling 17GB of user files. Both machines run Windows 2003 Server. I set up a domain root (called DATA) on ServerA and used a spare 5GB volume (drive E
to host the root. The data itself is in 4 folders on drive D. I then set up identical volumes on the other DC, ServerB, both for the data itself and also for the root. I initially set up replication of the user data and also the root going one way only from ServerA to ServerB. Users only have referral to ServerA.
This all worked very well for a while, but then I noticed that my E drive on ServerA was filling up, so I extended it and then extended it again and again! It is now 20GB capacity and nearly full. Remember, this is not the user file volume, just the root which in explorer contains 0 bytes!
So I stopped replication of the data and the root and set up a Robocopy script to keep my backup up to date on ServerB. Imagine my surprise when I found drive E still filling up! I ran Health-chk and sure enough, even though I don't understand all of the log files it produces, there is still ongoing FRS activity with my DFS name DATA.
So I tried deleting the DFS root, intending to rebuild it, but it won't let me remove it (access denied).
I would really appreciate any suggestions that anyone may have. Thanks.
to host the root. The data itself is in 4 folders on drive D. I then set up identical volumes on the other DC, ServerB, both for the data itself and also for the root. I initially set up replication of the user data and also the root going one way only from ServerA to ServerB. Users only have referral to ServerA.This all worked very well for a while, but then I noticed that my E drive on ServerA was filling up, so I extended it and then extended it again and again! It is now 20GB capacity and nearly full. Remember, this is not the user file volume, just the root which in explorer contains 0 bytes!
So I stopped replication of the data and the root and set up a Robocopy script to keep my backup up to date on ServerB. Imagine my surprise when I found drive E still filling up! I ran Health-chk and sure enough, even though I don't understand all of the log files it produces, there is still ongoing FRS activity with my DFS name DATA.
So I tried deleting the DFS root, intending to rebuild it, but it won't let me remove it (access denied).
I would really appreciate any suggestions that anyone may have. Thanks.
