Auteur de questions
Pb de synchronisation DSF server ( Recreation de folder apres suppression)

Discussion générale
-
Bonjour
nous avons deux servers 2012 en configuration DFS pour la replication de fichiers, notre soucis et que le owner d'un dossier des qu'il supprime un folder oiu un fichier apres un temps le dossier reaprait sur le server en question ,
comment verifier la replication ou bien comment supprimé cette config svp
mon test était de supprimé un dossier comme admin local pas de recreation !
merci
Partager C'est avancer : Votez!SVP
- Type modifié Nedeltcho PopovMicrosoft contingent staff jeudi 7 juin 2018 07:35
Toutes les réponses
-
-
-
Bonjour
WARNINGS (There are 3 warnings to report)<v:vmlframe class="er1a" src="#Warn1"></v:vmlframe> Pre-existing content is not replicated and is consuming disk
space.Affected replicated folders: DATA Description: During the initial replication process for replicated folder DATA, the DFS
Replication service identified pre-existing local content that was not present
on the primary member and moved the content to E:\DATA\DfsrPrivate\PreExisting.
The DfsrPrivate\Preexisting folder is a hidden system folder that is located
under the local path of the replicated folder. Content in the
DfsrPrivate\PreExisting folder will not be replicated to other members of the
replication group, nor will the content be deleted by the DFS Replication
service during any automatic clean-up.Last occurred:
Tuesday, May 15, 2018 at 10:18:55 AM (GMT1:00)Suggested action: If you want this content to be replicated to other members, move the content
into the replicated folder outside of the DfsrPrivate folder. If you want to
reclaim this disk space, delete the pre-existing content in the PreExisting
folder.<v:vmlframe class="er1a" src="#Warn1"></v:vmlframe> This member is waiting for initial replication for replicated
folder DATA.Affected replicated folders: DATA Partager C'est avancer : Votez!SVP
-
-
erreur sur le 2zm nœud
<v:vmlframe class="pm1" src="#Minus"></v:vmlframe><v:vmlframe class="er1" src="#Warn1"></v:vmlframe> WARNINGS
(There are 2 warnings to report)<v:vmlframe class="er1a" src="#Warn1"></v:vmlframe> Pre-existing content is not replicated and is consuming disk
space.Affected replicated folders: DATA Description: During the initial replication process for replicated folder DATA, the DFS
Replication service identified pre-existing local content that was not present
on the primary member and moved the content to E:\DATA\DfsrPrivate\PreExisting.
The DfsrPrivate\Preexisting folder is a hidden system folder that is located
under the local path of the replicated folder. Content in the
DfsrPrivate\PreExisting folder will not be replicated to other members of the
replication group, nor will the content be deleted by the DFS Replication
service during any automatic clean-up.Last occurred:
Tuesday, May 15, 2018 at 11:29:36 AM (GMT1:00)Suggested action: If you want this content to be replicated to other members, move the content
into the replicated folder outside of the DfsrPrivate folder. If you want to
reclaim this disk space, delete the pre-existing content in the PreExisting
folder.<v:vmlframe class="er1a" src="#Warn1"></v:vmlframe> This member is waiting for initial replication for replicated
folder DATA.Affected replicated folders: DATA Description: This member is waiting for initial replication for replicated folder DATA
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 Domain Services. After the member detects that it
is part of replication group, the member will begin initial replication.Last occurred:
Tuesday, May 15, 2018 at 11:29:36 AM (GMT1:00)Suggested action: Replication will begin after initial replication is complete. If this state
does not change, see The Microsoft Web SitePartager C'est avancer : Votez!SVP
-
-
Bonjour
pour le moment , nous avons désactiver la réplication, la partage point sur le nœud principal pour ne pas pénaliser les ends users
après des vérifications, les dossiers qui ne synchronisent pas c'étaient des dossiers ou l'héritage a été cassé
sur le nœud 2
merci
Partager C'est avancer : Votez!SVP
-
Bonjour
des idée svp, apres investigation , j'ai remarqué que le namespace du partage avait comme accès lecture seulement pour all user, j'ai ajouté les acces du coup le partage aparait sur les end user sachant que nous avons la config enumerate activée mon souci c'est que sur quelque dissossier partagé j'ai des acces qui 'apparaissent pas sur les end user alors
\\dfs-01\partage ==> Ok
\\dfs-02\partage ==> Ok
mais \\dfs\partage qui pointe sur les deux nœuds, quelque accès sautent et pourtant sur le physique 1 et 2 le partage des deux noued c'est ok
merci d'avance
Partager C'est avancer : Votez!SVP