SysVol replication (DFS-R): Difference between revisions
From SambaWiki
Mmuehlfeld (talk | contribs) (Added links and descriptions) |
m (/* grammar) |
||
Line 1: | Line 1: | ||
Samba in its current state doesn't support SysVol replication via DFS-R (Distributed File System 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 Currently advise administrators to use one of the following workarounds: |
||
* [[Rsync based SysVol replication workaround|Rsync based SysVol replication workaround]] (Samba DCs only): Quick setup, easy to configure. |
* [[Rsync based SysVol replication workaround|Rsync based SysVol replication workaround]] (Samba DCs only): Quick setup, easy to configure. |
Revision as of 12:09, 15 October 2016
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