Con più domande
Windows 2003 - DFSR Problems.

Discussione generale
-
Hello, we have a problem with a DFS environment.
We have 2 DC in the same lan, on which we enable DFS Namespace and DFS Replication for a shared folder. This was working fine from april 2012 till 10th july when something happened but we don't know what exactly. We don't have Event Error that could identify the problem, but the replication is no longer working.
When we run the diagnostic report from DFS MAnagement we receive 2 warnings for both servers: "This member is waiting for initial replication for replicated folder xxxx".
We made all the AD connection test and also the RPC Mapper test and there are no connection problems, we tried also to manually set one server as the primary server with dfsradmin MemberShip command but nothing is changed.
The O.S. on both server is Windows Server 2003 R2 SP2 Standard Edition.
The Warning Message in the diagnostic report result is: This member is waiting for initial replication for replicated folder FLDREDIR and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory. After the member detects that it is part of replication group, the member will begin initial replication.
These are the last lines in one of the Dfsr Logs:
20120724 18:51:09.757 2604 SRTR 400 [WARN] SERVER_EstablishSession Failed on connId:{C928E4FF-111B-4710-89B9-7BC0045895C9} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} Error:
+ [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:703 2604 C206 The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:1889 2604 C205 The content set is not ready]
20120724 18:51:10.538 4492 DOWN 3671 [ERROR] DownstreamTransport::EstablishSession Failed on connId:{FC35DC75-D6C5-4F14-A32C-439B43BD1CF7} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} Error:
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C207 A failure was reported by the remote partner]
+ [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C206 The content set is not ready]
20120724 18:51:10.538 4492 INCO 2588 InConnection::RestartSession Retrying establish contentset session. connId:{FC35DC75-D6C5-4F14-A32C-439B43BD1CF7} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} csName:FLDREDIR
20120724 18:51:10.538 4492 INCO 563 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C207 A failure was reported by the remote partner]
+ [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C206 The content set is not ready]
20120724 18:51:10.538 4492 ISYN 68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20120724 18:53:09.759 2604 SRTR 400 [WARN] SERVER_EstablishSession Failed on connId:{C928E4FF-111B-4710-89B9-7BC0045895C9} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} Error:
+ [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:703 2604 C216 The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:1889 2604 C215 The content set is not ready]
20120724 18:53:10.618 4492 DOWN 3671 [ERROR] DownstreamTransport::EstablishSession Failed on connId:{FC35DC75-D6C5-4F14-A32C-439B43BD1CF7} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} Error:
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C217 A failure was reported by the remote partner]
+ [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C216 The content set is not ready]
20120724 18:53:10.618 4492 INCO 2588 InConnection::RestartSession Retrying establish contentset session. connId:{FC35DC75-D6C5-4F14-A32C-439B43BD1CF7} csId:{5C2757AC-CF61-4DD5-AA3B-139AD101607F} csName:FLDREDIR
20120724 18:53:10.618 4492 INCO 563 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C217 A failure was reported by the remote partner]
+ [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3664 4492 C216 The content set is not ready]
20120724 18:53:10.618 4492 ISYN 68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.On one server there is Symantec Backup Exec 11.d running in the night and when it start the DFS Replication is stopped by the system... but this is from the day we configured DFS Replication, so we have many errors and warnings from april 2012 during backup operation: event ID 5002 (paused for backup or restore), event ID 5004, event ID 5014 (the request was canceled by a shutdown). We also have SEP client on both server with folder exceptions set to DFS Private and DFS Root.
Any suggestion?
Tutte le risposte
-
Ciao, questo è il forum in lingua italiana di Windows Server, se preferisci utilizzare la lingua inglese puoi inserire la domanda in questo forum:
Hi, this is the italian forum of Windows Server, if you prefer the English language you can enter your question in this forum:
http://social.technet.microsoft.com/Forums/en/category/windowsserver/
-
-
Per la richiesta in italiano la sezione è corretta.
Comunque dal messaggio di errore sembra che non sia più impostato un membro primario per la cartella replicata.
Prova ad eseguire le indicazioni presenti in questa discussione:
- Modificato Fabrizio-GMVP, Moderator mercoledì 25 luglio 2012 08:41
-
se esegui un
net stop ntfrs
seguito da un
net start ntfrs
su entrambi i server i warnings si ripropongono ?
Edoardo Benussi
Microsoft MVP - Management Infrastructure
edo[at]mvps[dot]org -
-
-
ho l'impressione che il backup schedulato non permetta al servizio di replica di completare tutte le sue operazioni cosa che invece accadrebbe quasi certamente se il backup venisse stoppato o schedulato con frequenza minore (ad esempio ogni 3 giorni) inoltre mi pare di capire che gli errori nel log compaiono perchè il server senza backup trova giù il servizio dfs del membro che sta backuppando.
io, per curiosità, proverei a stoppare il backup per verificare se la teoria è giusta.
ti lascio anche questa lettura che può servirti
http://www.symantec.com/connect/forums/backup-dfs-backup-exec-125
Edoardo Benussi
Microsoft MVP - Management Infrastructure
edo[at]mvps[dot]org -
-
-
Stamani ho fatto anche questo, ho ripulito tutto il contenuto delle cartelle staging e sono rimaste vuote per il problema di replica. Ho ripulito anche le cartelle "ConflictAnd Delete" su entrambe i server.
Tra le varie soluzioni adottate ho anche provato questa: http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/4e6ade2e-fac0-417d-b683-49554f1fd277/ relativamente alla parte finale postata da Shaon Shan.
-
-
-
Prova ad eseguire le verifiche consigliate in questo blogpost: http://blogs.technet.com/b/askds/archive/2008/07/15/five-common-causes-of-waiting-for-the-dfs-replication-service-to-retrieve-replication-settings-from-active-directory.aspx
-
-
A questo punto, se ancora non lo hai fatto, secondo me è il caso di provare a ricreare direttamente il gruppo di replica relativo alla cartella.
- Modificato Fabrizio-GMVP, Moderator giovedì 26 luglio 2012 22:44
-
Ciao Baro,
Abbiamo ancora la tua richiesta aperta nel Forum di Active Directory e Group Policy.
Ci sono stati sviluppi a seguito dei consigli ricevuti?
Grazie in anticipo di tenerci aggiornati sul tuo percorso,
Microsoft offre questo servizio gratuitamente, per aiutare gli utenti e aumentare il database dei prodotti e delle tecnologie. Il contenuto viene fornito “così come è” e non comporta alcuna responsabilità da parte dell'azienda.
-