@Jens

We truly appreciate the insights you have shared concerning Rsync in comparison to zaloha.sh. Many thanks once more.

@Jens

Many thanks for the clear and precise explanation. We are truly grateful.

You seem to have had problems with getting REV.NEW to work: The option --revNew must be given and the file to be REV.NEW-ed must be younger than the last run of Zaloha.sh (= implies that it was created directly in the backup directory).

If the file is older, then it will be REMOVE-ed, as this implies that it must have existed in the source directory before and somebody removed it from the source directory …

1) It has the interactivity (execute only after user’s confirmation) plus finer information about the actions. E.g. write of a new file is NEW and the update of an existing file is UPDATE. If you use the --color option, NEW will display black/white (less risky operation) and UPDATE will display red (overwriting = more risky operation = more attention needed). I am not aware that rsync would give you that level of detail.

2) rsync is memory-constrained as it builds its file lists in memory. Problems have been reported with huge directory trees. This script builds and processes its file lists as CSV files (= not memory-constrained).

3) it has been reported that Rsync is slower than cp when acting locally. This is caused by the fact that rsync has a checksum-computing function built-in that is active even when copying locally. This program invokes the operating system’s cp command directly.

4) integrations with other systems, needed changes, etc: a shell script has certain advantages over a binary program

@Aamir

You are correct, rsync is a more advanced tool with so many options. But you can employ zalohah.sh as a simple and easy-to-use backup tool.