Now I will test the 2-way synchronization of Unison to see if the setup is fully working. I use the full path to unison here ( /usr/bin/unison) just to go sure that cron knows where to find unison. This would run Unison every 5 minutes adjust it to your needs (see man 5 crontab Donations to the Unison project are gratefully accepted: Press return to continue.
UNISON SYNCHRONIZE HOW TO
See the documentation for the UNISONLOCALHOSTNAME environment variable for advice on how to correct this. If you see this message repeatedly, it may be because one of your machines is getting its address from DHCP, which is causing its host name to change between synchronizations. If the two replicas are identical, then no changes will be reported. This means that any files that are different will be reported as conflicts, and any files that exist only on one replica will be judged as new and propagated to the other replica.
Now we create a private/public key pair on : ssh-keygen -t dsaĮnter file in which to save the key (/root/.ssh/id_dsa): //server2//var/Unison will assume that the 'last synchronized state' of both replicas was completely empty. This can be achieved as follows: apt-get -y install unison openssh-server ssh nano 3 Creating A Private/Public Key Pair On server1 Unison has to be installed on server1 and server2 since we connect from server1 to server2 using SSH, we also need the SSH packages and I’ll install the nano editor for file editing on the shell. Login to both servers on the shell as root and start with step 2 “ Installing Unison“. I want to synchronize the directory /var/All commands in this tutorial are run as root user. In this tutorial I will use the following two Debian servers: Unison is a file-synchronization tool similar to rsync, the big difference is that it tracks/synchronizes changes in both directions, i.e., files changed on server1 will be replicated to server2 and vice versa. This tutorial shows how to set up file synchronization between two Debian 10 servers with Unison.
0 kommentar(er)
