triadagiga.blogg.se - Unison synch

#Unison synch install#

# Have to experiment to see if they can be increased again. # copymax & maxthreads params were set to 1 for easier troubleshooting.

#Unison synch install#

Install -o root -g root -m 0750 -d /root/.unison Please include this file into logrotate as the log size is not controlled. So we create the first ssh connection as a controlpath file in the location specified, all subsequent connections will reuse on the first connection.ĭo the following on DC1 so that you can check what happens during the sync. If the remote system enforces rate limits on incoming ssh connections, unison will fail if you try to run it this way. Ssh-copy-id -i ~/.ssh/id_rsa.pub can try to access DC2 via ssh (On Gentoo you need to do eselect unison to create the link)Ĭreating SSH Public Key and ssh-copy to DC2 ssh-keygen -t rsa

Install unison by using your package manager or compile from source.

You don't need to setup the rsync server.

Make sure, that you use a version that supports extended ACLs!

Install rsync by using your package manager or compile from source.

Setup on the Domain Controller with the PDC Emulator FSMO role

Sysvolsync log location /var/log/sysvol-sync.logĬhange the paths if your setup is different. Sysvol is located at /var/lib/samba/sysvol on both DC1 and DC2 As Compare to the rsync method, it is bidirectional. This HowTo describes a solution for SysVol replication, that is based on rsync and unison. Information on unison + rsync replication This HowTo provides a basic workaround solution based on rsync and unison. To achieve this important feature in a Multi-DC environment, until it's implemented, workarounds are necessary to keep it in sync. Samba AD currently doesn't provide support for SysVol replication.

3.1.4 Setup Unison defaults running parameters.

3.1.1 Creating SSH Public Key and ssh-copy to DC2.

3.1 Setup on the Domain Controller with the PDC Emulator FSMO role.

2 Information on unison + rsync replication.