Replication Problem between 2 Win2k3 R2 Servers
ftnico
The replication includes 5 shares with about 1 TB of data at all...
After the system worked perfectly for about 2 months, 3 of the 5 shares
started making problems.. not replicating new or changed files (small ones)..
or then just after a long time ...
I read that there's a limit with dfsr for the amount of data being shared..
Could this problem be, because it touched the limit of 1TB?
Rudolf Meier
No, there is no limit! Microsoft made the tests with 1 TB of data. But the
system can handle more data.
So... I'd say you have an other problem. Do you have logfile entries?? Or
also other problems?
Rudolf Meier
ftnico
"Rudolf Meier" wrote:
Not yet.. I'm having access to the system today.. and will have a look into
it..
Are there other Ms diag tools available ?
Rudolf Meier
Well... there are a lot. But if you don't know what you are searching it's
difficult. I think I would try to have a look at the "topology check" as a
first idea (in the dfs snapin). ... maybe it shows some problems. Because
what I could imagine is a dns problem or something and that's what this
diagnose will show... but... I've no other ideas currently... if it's not a
problem of the harddisk itself or of the machine. If you're running out of
memory or your cpu is used completly all the time... maybe this could also
lead to such problems... or... problems with your network cards... :-) ...
Rudolf
Jeffrey Randow
network log files and people keeping Excel spreadsheets open days at a
time...
---
Jeffrey Randow
jeffre...@gmail.com
Windows Networking MVP 2001-2006
http://www.networkblog.net
On Mon, 12 Nov 2007 09:15:41 +0100, "Rudolf Meier" <me...@gmx.net>
wrote:
ftnico
The 2 OS running on the 2 servers is x64... Could this be a hint?
The problems at the moment are:
- No Errors in the Eventlog except one.. (EventID 6002)
The DFS Replication service detected invalid msDFSR-Subscriber object data
while polling for configuration information.
- There are 6 shares configured for Replication... some of them have more
then 40'000 Folders in it. After DFS was running fine for 2 months..
Replication problems started about 10 days ago... on 3 of the 6 shares.. then
our client deleted the replication between these folders and reconfigured
it.. with the same names.. (I remember reading about this in a newsgroup..
that this could also make problems.. is this true? ). Since then.. in all of
these 3 shares..many files sitting in the preexisting or conflictanddeleted
folders..
- When we try to get out the confictanddeleted files and copy them to a
seperate folder.. and then move them back into the replicated shares, the new
files get overwritten with the old versions from the other server and the
newer files (which we tried to move in) get moved to the conflictanddeleted
folder again...
- Aswell, as we try to restore the files from the preexisting folder.. about
2GB.. it takes hours to be replicated to the other node..
btw: the nodes are connected by a 1GBit link....
Rudolf Meier
> The 2 OS running on the 2 servers is x64... Could this be a hint?
No, I don't think this is an x64 related problem... but having more
information never hurts :-).
> The problems at the moment are:
> - No Errors in the Eventlog except one.. (EventID 6002)
> The DFS Replication service detected invalid msDFSR-Subscriber object
> data
> while polling for configuration information.
That's the problem... at least to me it seems plausible, that this could be
the problem. I never had this error myself. But you can find some
information on the web and in this newsgroup on how to find out how to solve
this. I think, it would run again after solving this (as far as I know you
have to delete some entries in the AD with the ADSIEdit-utility).
Rudolf
DaveB
> > The problems at the moment are:
> > - No Errors in the Eventlog except one.. (EventID 6002)
> > The DFS Replication service detected invalid msDFSR-Subscriber object
> > data
> > while polling for configuration information.
>
> That's the problem... at least to me it seems plausible, that this could be
> the problem. I never had this error myself. But you can find some
> information on the web and in this newsgroup on how to find out how to solve
> this. I think, it would run again after solving this (as far as I know you
> have to delete some entries in the AD with the ADSIEdit-utility).
>
> Rudolf
One of the best threads I have found on this issue is located here:
http://www.eggheadcafe.com/aspnet_answers/windowsserverdfs_frs/Jul2006/post27481726.asp
Another thread that has more very good generic information is located here:
Hope those help
Patrick R.
registry setting change. I don't remember exactly where but I was increasing
the "staging" area for the DFS folders, and that fixed my problem. Also when
increasing the staging area try to determine all the other instances that may
increase the size above your expectations. For example, you have 1TB of data
in one share but for a while until things get synchronized you may want to
double up on the size for a while and then when things get settled you can
decrease the size of the staging area to some percentage larger than what you
need at the moment to allow for some type of growth. I know I don't have the
details, ah, I also remember that this is referenced in one of the Event
Viewer logs as well. This should point you to the right fix.