Both Monikop and Pokinom will create automatically any directories they need.


Put removable disks into Monikop's host on Rover and switch it on. Immediately, Monikop starts pulling data from Sources it can reach. Monikop will notice additional Sources that become reachable later and will start pulling data there as well.

For each Source, Monikop keeps starting over to see if there is new data. Only Monikop's shutdown or the disappearance of the data Source will end this cycle.

One removable disk is sufficient for Monikop's correct operation, but if speed is important, putting in as many disks as there are data Sources may be beneficial as Monikop uses them in parallel.

To end a session, press [F3] to shut down Monikop, and remove the disks. Monikop's display shows which disks are not yet used so you can avoid carrying empty disks around.


Put removable disks into Pokinom's host in office and switch it on. Immediately, Pokinom starts pushing data to Destination. Interrupting this by shutting down Pokinom early is not a problem as long as it is later given the opportunity to finish. Otherwise files, even those already copied to Destination, won't be deleted by Monikop from their removable disks during the next cycle.

Press [F9] to toggle whether or not you want Pokinom to shut down when finished.

File permissions in Destination's receiving directory must not be changed in a way that prevents the rsync server from modifying. Best practice is to move anything out of this directory prior to any processing.

Pokinom needs a sufficient amount of free disk space on Destination; it must be rebooted once this temporarily hasn't been the case.

Crash Recovery

Removable disks may get lost before they reach Destination, or Destination may crash shortly after receiving fresh data. The following may help in these cases.

Data Recovery from Source(s) on Rover

On Monikop's host, stop Monikop and delete the log files whose directory and name prefix is set in monikop.config by $rsync_log_prefix and $finished_prefix, and whose names resemble the Source they belong to.

On next startup, Monikop will pull all data from this Source again.

Data Loss on Destination: Recovery from Removable Disks

Data on removable disks are deleted not until the disk is finished by Pokinom and re-inserted in Monikop. (Non-)deletability is expressed by directory names defined in both monikop.config and pokinom.config:

Disk Failure

Suppose the system reports disk error on (say) /dev/sdb1. What is it's label?

ls -l /dev/disk/by-label

shows the mapping.