John
Guest
|
 Posted:
Thu Sep 01, 2005 12:52 am Post subject:
What to do when the database get corrupted. |
|
|
Configuration:
Server 1 (DC and holds the DFS root and where a copy of server2 files will
be placed)
Server 2 (Just a plain old server and where the original files are located)
I was in the process of setting up DFS-FRS between the above two servers.
I've been adding targets a few at a time to keep traffic down. I was just
about done when Server 2 crashed, problem with a controller, and it's DFS-FRS
database got corrupted. If I just deleted the database and let it get
recreated then DFS-FRS starts moving file back from Server 1 to Server 2.
Normally I could live with that , it just takes hours, except that not all of
the files had been rep to Server 1 yet. If I let the process complete this
would have cause files to be deleted from Server 2 and thus lost forever
unless restored from backup. To keep that from happening I killed all
replication deleted the targets and move the file from the "Pre" folder back
into each shared folder root.
Is there ANY way in a case like this to get Server 2 back in the rep ring
without transfering all the files back from Server 1 to Server 2? If not why
not? All the files are there it's just that DFS-FRS does not seem to know
that.
What I would think should happen would be that when Server 2 comes back
online it should figure out what files it already has and only move files
between servers that need to be updated. Why does it have to start over again
and move over 300GB of data? Seems dumb to me!
What am I missing here? |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in