Delete remote folder

Fabian Cenedese Cenedese at
Fri Jun 3 09:46:48 UTC 2016

At 10:27 02.06.2016, Fabian Cenedese wrote:
>Content-Transfer-Encoding: 7bit
>I'm trying to build a backup system based on rsync. It should
>work with different destinations (local, share, remote etc) that's
>why I'm looking for ways how every operation can be controlled
>from the client side.
>I want to create full backups and incremental backups. For the
>incremental backups I use --compare-dest lastfullbackup. This
>works nicely except that the whole directory tree is created
>even if no files are copied. This is mentioned several times
>on the Internet and the usual answer is that there's no way
>around it because of the way that rsync works. I don't mind
>that they are created if there's a (rsync-)way to delete them
>again afterwards, something like
>rsync -a --delete --prune-empty-dirs dest dest
>Unfortunately at least one place has to be local, doing a
>remote-remote is not possible.

So far I haven't found a solution to this problem. I've now seen
this release note for the last version 3.1.2:

- Don't create an empty backup dir for a transferred file that doesn't
      exist yet.

I'm wondering now if that would help in my case with --compare-dest.
But I don't have it compiled for Windows. Can anybody confirm if the
newest rsync does not create empty folders anymore?


bye  Fabi

More information about the rsync mailing list