SysVol replication (DFS-R): Difference between revisions
From SambaWiki
mNo edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
{{Imbox |
{{Imbox |
||
| type = warning |
| 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. |
| 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. |
||
}} |
}} |
||
Revision as of 15:45, 13 September 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:
- Rsync based SysVol replication workaround (Samba DCs only): Quick setup, easy to configure.
- 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 (Samba DCs only): More complex, requires third party script, each DC requires a cron job against each other DC
- Robocopy based SysVol replication workaround (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy
 | You need to sync idmap.ldb 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 idmap.ldb, you can and will get different IDs on each DC. You need to sync idmap.ldb when you first join a new DC and then regularly, to ensure the IDs remain constant, you do not need to sync idmap.ldb every time you sync SysVol. |