Contacting server...Connected [//primary_server_ip//home/primary_user/data -> //primary_server_ip//home/backup_user/data]Looking for changesWarning: No archive files were found for these roots, whose canonical names are: /home/primary_user/data //backup_server_ip//home/backup_user/dataThis can happen eitherbecause this is the first time you have synchronized these roots, or because you have upgraded Unison to a new version with a differentarchive format. Update detection may take a while on this run if the replicas are large.Unison will assume that the 'last synchronized state' of both replicaswas completely empty. This means that any files that are differentwill be reported as conflicts, and any files that exist only on onereplica will be judged as new and propagated to the other replica.If the two replicas are identical, then no changes will be reported.If you see this message repeatedly, it may be because one of your machinesis getting its address from DHCP, which is causing its host name to changebetween synchronizations. See the documentation for the UNISONLOCALHOSTNAMEenvironment variable for advice on how to correct this.Donations to the Unison project are gratefully accepted: http://www.cis.upenn.edu/~bcpierce/unison Waiting for changes from serverReconciling changesdir ----> / Propagating updatesUNISON 2.48.3 started propagating changes at 16:30:43.70 on 03 Apr 2019[BGN] Copying from /home/primary_user/data to //backup_server_ip//home/backup_user/data[END] Copying UNISON 2.48.3 finished propagating changes at 16:30:43.71 on 03 Apr 2019Saving synchronizer stateSynchronization complete at 16:30:43 (1 item transferred, 0 skipped, 0 failed)
Contacting server...Connected [//primary_server_ip//home/primary_user/data -> //backup_server_ip//home/backup_user/data]Looking for changes Waiting for changes from serverReconciling changesNothing to do: replicas have not changed since last sync.
Contacting server...Connected [//primary_server_ip//home/primary_user/data -> //backup_server_ip//home/backup_user/data]Looking for changes Waiting for changes from serverReconciling changeschanged ----> file1 Propagating updatesUNISON 2.48.3 started propagating changes at 16:38:37.11 on 03 Apr 2019[BGN] Updating file file1 from /home/primary_user/data to //backup_server_ip//home/backup_user/data[END] Updating file file1UNISON 2.48.3 finished propagating changes at 16:38:37.16 on 03 Apr 2019Saving synchronizer stateSynchronization complete at 16:38:37 (1 item transferred, 0 skipped, 0 failed)
您现在可以运行Unison来备份目录。在下一步中，您将通过运行Unison with cron来自动执行备份过程。
# Edit this file to introduce tasks to be run by cron.# # Each task to run has to be defined through a single line# indicating with different fields when the task will be run# and what command to run for the task# # To define the time you can provide concrete values for# minute (m), hour (h), day of month (dom), month (mon),# and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system# daemon's notion of time and timezones.# # Output of the crontab jobs (including errors) is sent through# email to the user the crontab file belongs to (unless redirected).# # For example, you can run a backup of all your user accounts# at 5 a.m every week with:# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/# # For more information see the manual pages of crontab(5) and cron(8)# # m h dom mon dow command