SysVol replication (DFS-R): Difference between revisions
From SambaWiki
m (/* grammar) |
m (/* remove line) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 7: | Line 7: | ||
* [[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 |
* [[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 |
* [[Robocopy_based_SysVol_replication_workaround|Robocopy based SysVol replication workaround]] (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy |
||
[[Category:Active Directory]] |
|||
Revision as of 15:36, 25 March 2019
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