SysVol replication (DFS-R): Difference between revisions

From SambaWiki
(New, small page about Sysvol replication via DFS-R)
 
m (Added information about idmap.ldb sync frequency)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Samba in its current state doesn't support SysVol replication via DFS-R (Distributed File System Replication). Neither it supports the older FRS (File Replication Service) used in Windows Server 2000/2003 for Sysvol replication.
Samba in its current state doesn't support SysVol replication via DFS-R (Distributed File System Replication) or the older FRS (File Replication Service) used in Windows Server 2000/2003 for Sysvol replication.


Currently we advice administrators to use one of the following, easy to setup workaround:
We Currently advise administrators to use one of the following workarounds:


* [[Rsync_based_SysVol_replication_workaround|Rsync based SysVol replication]] - quick setup, easy to configure on additional DCs.
* [[Rsync based SysVol replication workaround|Rsync based SysVol replication workaround]] (Samba DCs only): Quick setup, easy to configure.
* [[Bidirectional Rsync/Unison based SysVol replication workaround|Bidirectional Rsync/Unison based SysVol replication workaround]] (Samba DCs only): More complex, requires third party script, each DC requires a cron job against each other DC
* [[Bidirectional Rsync/osync based SysVol replication workaround|Bidirectional Rsync/osync based SysVol replication workaround]] (Samba DCs only): More complex, requires third party script, each DC requires a cron job against each other DC
* [[Robocopy_based_SysVol_replication_workaround|Robocopy based SysVol replication workaround]] (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy



* [[Bidirectional_Rsync/Unison_based_SysVol_replication_workaround|Bidirectional Rsync/Unison based SysVol replication]] - more complex setup, requires third party script, each DC requires cronjobs against each other DC
{{Imbox
| type = warning
| text = You need to sync <code>idmap.ldb</code> from the DC holding the PDC_Emulator FSMO role to all other DCS. This ensures that all DCs will use the same IDs. If you do not sync <code>idmap.ldb</code>, you can and will get different IDs on each DC. You need to sync <code>idmap.ldb</code> when you first join a new DC and then regularly, to ensure the IDs remain constant, you do not need to sync <code>idmap.ldb</code> every time you sync SysVol but as stated in the mailing list it should be done periodically.
}}





[[Category:Active Directory]]

Latest revision as of 15:57, 6 December 2023

Samba in its current state doesn't support SysVol replication via DFS-R (Distributed File System Replication) or the older FRS (File Replication Service) used in Windows Server 2000/2003 for Sysvol replication.

We Currently advise administrators to use one of the following workarounds: