| Author |
Message |
Ben
Guest
|
 Posted:
Thu Oct 14, 2004 12:47 pm Post subject:
Replication Problem |
|
|
Hi,
We have just setup a 2nd server (server2, win2k server sp4), which is
running DFS to provide fault tolerance to our main server. I setup about 20
or so DFS links, with DFS replicas. I.e. \\server1\sales which is master,
and \\server2\sales which was added as a replica. So far its replicated
about 15 or so of the links from server1 to server2 however its now just
stopped, and I can't get it to replicate anymore. The remaining 5 links,
have a few files inside which look to have been replicated, but not
everything. During the replication process I set SERVER1 as a root replica
of SERVER2, to make sure it was fully fault tolerant.
In the event log I'm getting: Event ID: 13508 Event Source: NtFrs Computer:
SERVER2.
There are 4 or 5 entries like this, 1 for each of the 5 folders it
hasn't replicated i.e. e:\data\rsgfiles e:\data\sales e:\data\it etc
Description:
The File Replication Service is having trouble enabling replication from
SERVER1 to SERVER2 for e:\data\rsgfiles using the DNS name
SERVER1.ourdomain.gb. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name SERVER1.ourdomain.gb from
this computer.
[2] FRS is not running on SERVER1.ourdomain.gb.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Now I can ping SERVER1 using its FQDN so I'm sure DNS is fine, FRS is
running on SERVER1, I've even stopped and restarted it, I'm not sure about
the topology information, it should have replicated, we only have 3 DCs (all
win2k) and all in the same room. I have looked on eventid.net for 13508 &
NtFrs and tried some of the idea there, including NTFRSUTL VERSION
SERVER1.ourdomain.gb to verify that FRS is running on it, I've run netdiag
/fix to correct missing DNS SRV records. And I've also re-installed SP4, on
it just to make sure.
Could setting SERVER1 as a root replica to SERVER2 have caused this? I was
getting a few errors saying the staging area was full which I think was due
to having some very large files (over 650mb). So I changed the regisry value
HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Staging Space Limit
in KB to double the decimal value. Could this have caused it?
Any help greatly appreciated.
--
Ben
IT Professional, MCP 70-210
"On my way to becoming fully certifiable!" |
|
| Back to top |
|
 |
Glenn LeCheminant
Guest
|
| Posted:
Sat Oct 16, 2004 10:19 pm Post subject:
Re: Replication Problem |
|
|
Ben,
FRS is a very sensitive technology and is not so resilient when changes are
being made to the topology during initial replication.
This "During the replication process I set SERVER1 as a root replica
| Quote: | of SERVER2" is likely the culprit behind the now failing replication.
13508s are sometimes the most difficult to resolve because they are so |
vague.
To get to the bottom of what is causing the 13508s, you need to download and
install FRSDIAG.
Then run it against the Server2.
Examine the output for errors, then research resolution.
The FRS technical reference is an excellent article if you are interested in
the nuts and bolts of FRS.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/W2K3TR_frs_intro.asp
The shotgun approach to fixing this one is to restore the replica set.
D4 server 1
D2 server 2
if you don't know what this means, search for "burflags" on the net.
Of course, if the root cause of the failure is networking related, the D4/D2
process will not fix that.
Glenn
"Ben" <bjblackmore@nospam.hotmail.com> wrote in message
news:uv4dUIcsEHA.2128@TK2MSFTNGP11.phx.gbl...
| Quote: | Hi,
We have just setup a 2nd server (server2, win2k server sp4), which is
running DFS to provide fault tolerance to our main server. I setup about
20
or so DFS links, with DFS replicas. I.e. \\server1\sales which is master,
and \\server2\sales which was added as a replica. So far its replicated
about 15 or so of the links from server1 to server2 however its now just
stopped, and I can't get it to replicate anymore. The remaining 5 links,
have a few files inside which look to have been replicated, but not
everything. During the replication process I set SERVER1 as a root replica
of SERVER2, to make sure it was fully fault tolerant.
In the event log I'm getting: Event ID: 13508 Event Source: NtFrs
Computer:
SERVER2.
There are 4 or 5 entries like this, 1 for each of the 5 folders it
hasn't replicated i.e. e:\data\rsgfiles e:\data\sales e:\data\it etc
Description:
The File Replication Service is having trouble enabling replication from
SERVER1 to SERVER2 for e:\data\rsgfiles using the DNS name
SERVER1.ourdomain.gb. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name SERVER1.ourdomain.gb from
this computer.
[2] FRS is not running on SERVER1.ourdomain.gb.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Now I can ping SERVER1 using its FQDN so I'm sure DNS is fine, FRS is
running on SERVER1, I've even stopped and restarted it, I'm not sure about
the topology information, it should have replicated, we only have 3 DCs
(all
win2k) and all in the same room. I have looked on eventid.net for 13508 &
NtFrs and tried some of the idea there, including NTFRSUTL VERSION
SERVER1.ourdomain.gb to verify that FRS is running on it, I've run netdiag
/fix to correct missing DNS SRV records. And I've also re-installed SP4,
on
it just to make sure.
Could setting SERVER1 as a root replica to SERVER2 have caused this? I was
getting a few errors saying the staging area was full which I think was
due
to having some very large files (over 650mb). So I changed the regisry
value
HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Staging Space
Limit
in KB to double the decimal value. Could this have caused it?
Any help greatly appreciated.
--
Ben
IT Professional, MCP 70-210
"On my way to becoming fully certifiable!"
|
|
|
| Back to top |
|
|
Ben
Guest
|
| Posted:
Mon Oct 18, 2004 4:59 pm Post subject:
Re: Replication Problem |
|
|
Glenn,
Thanks for the reply. I will download FRSDIAG now and run it. I will also
read the technical reference this lunch time.
I think I screw DFS up when I create the root, then deleted it and created
another. There seems to be some references to the old root in some of the
error logs. Might just be quicker to blat the server and re-install. Its
only a test server at the moment, luckily!
Cheers
Ben
"Glenn LeCheminant" <the.only@gmail.com> wrote in message
news:eAtEsR6sEHA.376@TK2MSFTNGP09.phx.gbl...
| Quote: | Ben,
FRS is a very sensitive technology and is not so resilient when changes
are
being made to the topology during initial replication.
This "During the replication process I set SERVER1 as a root replica
of SERVER2" is likely the culprit behind the now failing replication.
13508s are sometimes the most difficult to resolve because they are so
vague.
To get to the bottom of what is causing the 13508s, you need to download
and
install FRSDIAG.
Then run it against the Server2.
Examine the output for errors, then research resolution.
The FRS technical reference is an excellent article if you are interested
in
the nuts and bolts of FRS.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/W2K3TR_frs_intro.asp
The shotgun approach to fixing this one is to restore the replica set.
D4 server 1
D2 server 2
if you don't know what this means, search for "burflags" on the net.
Of course, if the root cause of the failure is networking related, the
D4/D2
process will not fix that.
Glenn
"Ben" <bjblackmore@nospam.hotmail.com> wrote in message
news:uv4dUIcsEHA.2128@TK2MSFTNGP11.phx.gbl...
Hi,
We have just setup a 2nd server (server2, win2k server sp4), which is
running DFS to provide fault tolerance to our main server. I setup about
20
or so DFS links, with DFS replicas. I.e. \\server1\sales which is
master,
and \\server2\sales which was added as a replica. So far its replicated
about 15 or so of the links from server1 to server2 however its now just
stopped, and I can't get it to replicate anymore. The remaining 5 links,
have a few files inside which look to have been replicated, but not
everything. During the replication process I set SERVER1 as a root
replica
of SERVER2, to make sure it was fully fault tolerant.
In the event log I'm getting: Event ID: 13508 Event Source: NtFrs
Computer:
SERVER2.
There are 4 or 5 entries like this, 1 for each of the 5 folders it
hasn't replicated i.e. e:\data\rsgfiles e:\data\sales e:\data\it etc
Description:
The File Replication Service is having trouble enabling replication from
SERVER1 to SERVER2 for e:\data\rsgfiles using the DNS name
SERVER1.ourdomain.gb. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name SERVER1.ourdomain.gb
from
this computer.
[2] FRS is not running on SERVER1.ourdomain.gb.
[3] The topology information in the Active Directory for this replica
has
not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the
problem
is fixed you will see another event log message indicating that the
connection has been established.
Now I can ping SERVER1 using its FQDN so I'm sure DNS is fine, FRS is
running on SERVER1, I've even stopped and restarted it, I'm not sure
about
the topology information, it should have replicated, we only have 3 DCs
(all
win2k) and all in the same room. I have looked on eventid.net for 13508
&
NtFrs and tried some of the idea there, including NTFRSUTL VERSION
SERVER1.ourdomain.gb to verify that FRS is running on it, I've run
netdiag
/fix to correct missing DNS SRV records. And I've also re-installed SP4,
on
it just to make sure.
Could setting SERVER1 as a root replica to SERVER2 have caused this? I
was
getting a few errors saying the staging area was full which I think was
due
to having some very large files (over 650mb). So I changed the regisry
value
HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Staging Space
Limit
in KB to double the decimal value. Could this have caused it?
Any help greatly appreciated.
--
Ben
IT Professional, MCP 70-210
"On my way to becoming fully certifiable!"
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in