Difference between revisions of "Talk:Rsync based SysVol replication workaround"

From SambaWiki
(→‎sysvolreset: new section)
m (Mmuehlfeld moved page Talk:SysVol Replication to Talk:Rsync based SysVol replication workaround: Rename page for better wiki structure)
(No difference)

Revision as of 20:05, 25 August 2015

We are running 2 Samba domain controllers with rsync replication on Debian 7 (master) and Ubuntu 14.04.2 LTS (slave). The sysvol share on slave DC runs into problems after each replication. The NTACL seems to be broken. It is not possible to access the share via smb/network.

We fixed this issue by adding

samba-tool ntacl sysvolreset

command after the rsync command.

The full cron looks like:

*/5 * * * *          rsync -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ \
                     /path/to/your/sysvol/folder/ > /dev/null && samba-tool ntacl sysvolreset &> /dev/null


The workaround with sysvolreset shouln't be necessary and will break your ACLs on the share, if it's not default. Make sure, that you have Make sure, that you have identical IDs on build-in groups. I've added a note to the page, too.