On 11-08-18 18:00, Henri Derksen wrote:
> But what happens when at the destination there is a file called ProjectX,
> and on the source media it became a directory called ProjectX, with several
> files more in them.
> Is then de original file ProjectX deleted before making a directory ProjectX
at
> the destination, or does rsync give an error that the directory ProjectX
cannot
> be created, as there is already a file with that name?
> Then te backup copy process is interrupted for an answer to gon on.

The second, but the process is not interrupted, it simply gives an error
message and continues. This happens sometimes with my backups, down in
far away hidden program settings directories, where for some reason
files changed to directories. Sometimes it bothers me and I manually
delete the file from the backup disk and rerun the backup so that the
directory may now be copied. Most of the time I can't be bothered. The
goal of my backups is not to have a drop-in replacement but to save
important data (and apps, settings, etc) which I need to rebuild my
system from scratch. If (when...) the system disk fails, I always feel
happier to start with a fresh installation and add from there.

rsync never resolves conflicts, it only does what you tell it to do.
There is an overwhelming amount of options, see 'man rsync'. In the end
though, I only use -au and some excludes:
https://github.com/ednl/shellscripts/blob/master/bak (Since I only use
the disks for backups and never edit those files, the -u option is
actually unnecessary. Ah well.) If you decide that you need some form of
--delete* option, MAKE SURE TO TEST IT FIRST with the -n option or you
could lose important parts of your backup. Happened to me once :( but
never again.

> MG> There is a related program, rsnapshot, [...]
>
> Did you test this?

Millions of people tested this. rsnapshot is based on rsync. OS X
TimeMachine is sort of based on rsnapshot.

--- SoupGate-Win32 v1.05