Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Windows Server General Help » FRS (File Replication Service) - Strange Issue
FRS (File Replication Service) - Strange Issue [message #164169] Tue, 16 June 2009 16:17 Go to next message
granjan  is currently offline granjan  United States
Messages: 12
Registered: July 2009
Junior Member
I have a Widnows 2003 domain controller that the system partition was on 2
mirrored drives initially and at some point the mirror was broken leaving a
separate C: and E: drive (D: is a RAID volume). This server is at a remote
office so I haven't been able to get there yet to recreate the mirror.

The strangeness started yesterday when I decided to delete all the data off
the E: drive to use for some temporary storage until I can fix the mirror
set. What I ended up finding out is that FRS has been replicating the
netlogon directory to both the C: AND the E: drive since the mirror was
broken and once the scripts folder was deleted from E: it replicated the
changes to all the other domain controllers and blew away all the logon
scripts! For the life of me I can not find where the link to E: is being
stored or figure out how to remove it.

I saw something like this once before where I made a copy of the sysvol
folder to the desktop for a temporary backup when I was making some script
modifications and then deleted it off the desktop and the scripts were
deleted from the system volume at the same time! It appears that there is a
reference to sysvol that sticks whether it's a copy or not.

I've done plenty of searching in the MSKB and Google and can't find the
answer. Any suggestions would be greatly appreciated!

Thanks!
RWK
Re: FRS (File Replication Service) - Strange Issue [message #164214 is a reply to message #164169] Wed, 17 June 2009 21:11 Go to previous message
DaveMills  is currently offline DaveMills  United Kingdom
Messages: 335
Registered: July 2009
Senior Member
In the C:Windows\SYSVOL folder there is a folder called Domain and another
called SYSVOL which is shared. The shared SYSVOL contains "yourdomain.com"

"Domain" and "yourdomain.com" point to the same physical folder.
"yourdomain.com" is a Reparse point (or Junction). However if you backup
c:\windows\sysvol then restore it somewhere else the reparse point can get
restored to the new location but still points to the original folder. Thus you
now have something like

C:\WINDOWS\SYSVOL\DOMAIN (a folder)
C:\WINDOWS\SYSVOL\SYSVOL\yourdomain.com (a reparse point directing to the above
folder)
C:\restored_backup\SYSVOL\SYSVOL\yourdomain.com (a reparse point directing to
the same folder as above)

Now whatever change you make in any of the above folder paths will show up in
the other paths because as they are reparse points there is actually only one
physical copy.

When your mirror broke E: had a copy of the reparse point for SYSVOL\Domain
which pointed to the C: version, hence the symptoms you observed.

How I wish that Explorer used a different icon for a reparse point so you could
see it was not the real folder, like offline files does.

Use DIR to see <DIR> or <JUNCTION> against the folders.
Use Res kit utility LinkD.exe to manage them.


On Tue, 16 Jun 2009 15:17:33 -0500, "RWK" <me@nowhere.com> wrote:

>I have a Widnows 2003 domain controller that the system partition was on 2
>mirrored drives initially and at some point the mirror was broken leaving a
>separate C: and E: drive (D: is a RAID volume). This server is at a remote
>office so I haven't been able to get there yet to recreate the mirror.
>
>The strangeness started yesterday when I decided to delete all the data off
>the E: drive to use for some temporary storage until I can fix the mirror
>set. What I ended up finding out is that FRS has been replicating the
>netlogon directory to both the C: AND the E: drive since the mirror was
>broken and once the scripts folder was deleted from E: it replicated the
>changes to all the other domain controllers and blew away all the logon
>scripts! For the life of me I can not find where the link to E: is being
>stored or figure out how to remove it.
>
>I saw something like this once before where I made a copy of the sysvol
>folder to the desktop for a temporary backup when I was making some script
>modifications and then deleted it off the desktop and the scripts were
>deleted from the system volume at the same time! It appears that there is a
>reference to sysvol that sticks whether it's a copy or not.
>
>I've done plenty of searching in the MSKB and Google and can't find the
>answer. Any suggestions would be greatly appreciated!
>
>Thanks!
>RWK
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Previous Topic:NTFS permissions
Next Topic:NT Backup Issues
Goto Forum:
  


Current Time: Sun Aug 20 05:51:19 EDT 2017

Total time taken to generate the page: 0.02760 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software